Re:Legit: Git Workflow for Humans
by johnbellone on Friday August 03, 2012 @09:28AM
(#4333883)
I completely agree with your first point, but I do think that the majority of people using git probably don't have more than a single remote. I am sure there are those few people that are tasked with pulling (and hopefully, pushing) to the upstream, and likely a deployment remote like Heroku probably exists behind some process or script.
I do think that the majority of people using git probably don't have more than a single remote
Strong disagree. Nowadays the majority of git-users probably interacts with github. Just count the number of "Fork me on github"-ribbons that you come across on any given day.
The github workflow for forking a repository[1] involves two remotes (origin and upstream).
Just use 'git push heroku' to deploy then. Legit doesn't break existing git commands.
Re:Legit: Git Workflow for Humans
by kenneth_reitz on Friday August 03, 2012 @07:10PM
(#4336676)
Exactly.
1. Only 1 git remote? I need at least `master` and `heroku` for all of my projects, and often I'll need one or two extra `github` remotes for other forks/collaborators.
2. I wish it had pictures of what exactly it was doing (git graph-style stacks of commits before/after each commit).