Skip to content
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

-C option #66

Open
matiasdecarli opened this issue Jun 30, 2014 · 6 comments
Open

-C option #66

matiasdecarli opened this issue Jun 30, 2014 · 6 comments

Comments

@matiasdecarli
Copy link

Hi guys! I've forked the task and added the -C option in order to make this work properly in my build process. I would like to know if this is something that you would like to include on your version. In this case, I can finish it and send a pull request.

Cheers!

@rubenv
Copy link
Owner

rubenv commented Jun 30, 2014

Which task are you referring to? What does -C do?

@matiasdecarli
Copy link
Author

Sorry about the delay. Currently im implementing the -C in the push & commit tasks, but it could be added to a couple more tasks.

The idea of the -C is to excecute the task in another directory rather than the current one. A good example would be "git -C package push origin master ", pushing the repo thats inside "package" folder

@rubenv
Copy link
Owner

rubenv commented Jul 4, 2014

How does this relate to the grunt cwd option?

@matiasdecarli
Copy link
Author

I guess they output the same thing

@dylancwood
Copy link
Collaborator

It is true that they do the same thing. However, I am in support of merging this, as the -C option more closely resembles the git CLI API, as per #44.

@rubenv
Copy link
Owner

rubenv commented Jul 18, 2014

However, I am in support of merging this, as the -C option more closely resembles the git CLI API, as per #44.

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants