>there's a need for a tool that will automate and enforce git workflows. Beyond branches and remotes? Yeah, because most branching and merging in a team settin

>there's a need for a tool that will automate and enforce git workflows. Beyond branches and remotes? Yeah, because most branching and merging in a team setting follows a policy. That branch/merge strategy (and naming) is based upon a whole host of things including testing strategies, release schedules, issue tracker used, code review policies, how much you need bisect, etc. Git is entirely indifferent to those workflows and is as happy to let you follow it as it is to let you commit and push directly to the master branch with a commit message of "fixed shit". >Checking out branches and git add/status/diff/commit/push is that time consuming not only would you need to create a shortcut, other devs would opt-in to it? Yeah, when you add stashing, changing to the correct branches, rebasing and pushing, changing back and unstashing it actually does get tedious, especially since I needed to run it about 20 times a day. I actually didn't even create the script for them originally, I created it for me and they just started using it.