Repository navigation
Thoughts about --auto-pull --auto-push flags? #41
Description
Activity
I have use a similar set up. I have many repos for a given project and its dependencies, and want to do bulk operation across all of them. Typically a Pull as I manually go through each's changes for commits/push.
I do have a script that does a Pulls each repo, and typically I have to intervene as there are conflicts, or it wont pull due to uncommitted changes.
I think moving forwards with the Pull option would be helpful in both scenarios, just updating all repos and your pull/push one.
As for the Push, personally i would want all or nothing in that transaction. If there is a procedure you see that will check all repos, before pushing, that might make it safer.
So @badele what do you think about this change? I would love to make a PR!
@N2OMatt, I think, that is a good idea. do you think a hook system will not a good solution ? what do you think ?
Sample :
pull-hook
push-hook
etc ..We can will use a configuration file or param file.
--push-hook=mypush-scriptSample mypush-script
#!/bin/bash if [ $1 == "projectname" ]; then git push origin master fiIf we use hook solution, i think we can respond for all users imaginations :)
What do you think ?
@badele I think that's great!
Much more flexible than my proposal ;DSome quick questions:
- If the script isn't found is a fatal error or we just report it and continue?
- If the script itself returns an error, it should be treated as fatal or just report it?
- Should we provide short flags for those operations? (I think not, but just in case)
- What arguments we should pass to script?
$1 -> projectname $2 ->projectpath $3 -> currbranch?
Any further ideas??
@N2OMatt
If the script isn't found is a fatal error or we just report it and continue?
I think just report (for notify user that this feature exists :) ). Because some users they havent' need this feature
If the script itself returns an error, it should be treated as fatal or just report it?
I think just report and continue
Should we provide short flags for those operations? (I think not, but just in case)
No need flag, the gitcheck script just check if the file exists, this method can be change in the future
What arguments we should pass to script? $1 -> projectname $2 ->projectpath $3 -> currbranch?
I think, just the folder name, the users can call git command from this folder. The imagination of the user will do the rest :)
Hey ;D
I'm a "heavy" user of gitcheck... and I love it ;D
I work on multiple computers everyday - my laptop, my desktop, the company desktop,
and every once in a while, a remote server. Since I'm working at same projects
in all of them I constantly have to push all my changes and pull as well.
So, I run
gitcheck --remote --quietjust to discover the repos thathave changed and after that I need go to every repo and push/pull accordingly.
That's sucks a lot... I mean the gitcheck is doing its job great but yet I
need do a lot of manual stuff :/
With that in mind, I implemented a crude --auto-push and --auto-pull flags.
They work like that:
Yep, that's it... nothing fancy at this stage. But something interesting can
be worked out... like:
I don't know if it's very specific to my work flow, or other ppl might
have similar "issues" with that - and if do you want something like that
in gitcheck at first place.
If it's something that sounds good to you I can refine my work in about 3,4 days
and submit a pull request ;D
Tell me what you think about it!
Cheers and thanks for gitcheck!