eastein/gitwrench — Issue #3: automation of pushes/pulls
Author: eastein
Created: 2011-12-27 22:28:29+00:00
State: open

One of the reasons I wanted to write gitwrench was to avoid all the minutae of working with git for some patterns. One of them is pulling/pushing all the code when you get around to it, and not doing it individually. Right now gitwrench is entirely an inspection/query tool, and takes no actions.

# Push/Pull/Both

Options:

TODO determine if I want to distinguish between pull and fetch here, or just do pulls.

* do all pulls automatically unless local changes
* do all pulls automatically even if local changes, and report success or failure at automatic merges
* do all pushes automatically unless remote changes (git won't even do it if the remote has changed, all merging must be local). The same holds for git-svn clones. TODO determine if I need remote SVN server head querying before I can implement this feature.
* show only the actions that would be taken
* flag to make anything that would have been done that has effects ask the user (y/n) before continuing.

TODO determine what the options on the command line would be. Any use of these options will conflict with setting the cache duration as it is forced to ignoring local caches for the purpose of the commands anyway. Also, I must determine if I'd have to flush the caches of anything being pushed/pulled using this command.