We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am using runme in a monorepository. The challenge is that runme scans my entire repository for tasks.
The default behavior should likely be the current directory, and down; rather than up to .git.
.git
There should be a flag to support the entire repository: runme --git
runme --git
The text was updated successfully, but these errors were encountered:
Any chance your mono-repo is public? Could you point me to it, @rawkode?
Fwiw, you can use runme --project ./subdir or runme --project . to hard restrict it's discovery to a subdir.
runme --project ./subdir
runme --project .
Sorry, something went wrong.
It is, but I was only going through every service yesterday adding all my runme tasks. I'll push them up today
https://github.com/rawkodeacademy/rawkodeacademy
My feeling is that the current directory and down should be the default scope for tasks, this is what I and hopefully others would expect
I feel the flag should be to used to expand that scope, not restrict it
Hopefully others can share their thoughts
sourishkrout
No branches or pull requests
I am using runme in a monorepository. The challenge is that runme scans my entire repository for tasks.
The default behavior should likely be the current directory, and down; rather than up to
.git
.There should be a flag to support the entire repository:
runme --git
The text was updated successfully, but these errors were encountered: