-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
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
support cwd #198
Labels
Comments
Initially I was going to say no to this as it such an odd edge case but implementation will probably take less time than writing this comment. Ok maybe not but its probably not far off. All thats needed is to pass an options object to the exec commands that takes cwd if it exists.
Something like that. If you want to submit a PR, then go ahead and there is a high chance it will get merged. |
mojoaxel
added a commit
to mojoaxel/grunt-bump
that referenced
this issue
Jan 18, 2017
With the new option `cwd` it is possible to define a custom working directory. This is usefull if you want to pump e.g a sub-component or simply for testing. Closes vojtajina#198
mojoaxel
added a commit
to mojoaxel/grunt-bump
that referenced
this issue
Jan 22, 2017
With the new option `cwd` it is possible to define a custom working directory. This is usefull if you want to pump e.g a sub-component or simply for testing. Closes vojtajina#198
mojoaxel
added a commit
to mojoaxel/grunt-bump
that referenced
this issue
Jan 22, 2017
With the new option `cwd` it is possible to define a custom working directory. This is usefull if you want to pump e.g a sub-component or simply for testing. Closes vojtajina#198
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a need to issue the git tag commands in a particular directory different than the directory where the grunt commands are issued. Can you add cwd support to grunt-bump.
The text was updated successfully, but these errors were encountered: