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

Git pull #24

Open
jarbot opened this issue Oct 21, 2013 · 5 comments
Open

Git pull #24

jarbot opened this issue Oct 21, 2013 · 5 comments
Labels

Comments

@jarbot
Copy link

jarbot commented Oct 21, 2013

Maybe I'm using this plugin improperly but it seems like it would be handy to have a git pull feature.

@rubenv
Copy link
Owner

rubenv commented Oct 21, 2013

Not currently supported but easily added. Like gitclone, the pain with this one is testing, which I'm trying to reduce with #23.

@plus-
Copy link

plus- commented Oct 23, 2013

This one would be really usefull (or fetch + merge) to use for CI purpose on some github hook. I'd like to see it.

@daslicht
Copy link

git pull would be lovely :) especially if we would have lets say an automatic interval of 5 minutes :)

@clemens-tolboom
Copy link

Should this issue be closed as the README.md has a https://github.com/rubenv/grunt-git#the-gitpull-task ?

@timondavis
Copy link

I can't seem to point git-pull at the same directory I cloned my project into (I'm trying to write a script that will help green devs manage their code base for my company - it would be ideal to use the same gruntfile for management even though its outside of the repo). For example, I make the grunt file in /my/path and then have it download to /my/path/repo. I want to then have a gitpull directive that has the code in /my/path/repo pull from origin. Am I missing something? If that isn't possible right now, I submit that it should be a feature.

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

No branches or pull requests

6 participants