Re:The Three Great Virtues of a Programmer: Laziness, Impati...
by nawitus on Saturday June 27, 2015 @01:14PM
(#9790787)
You can use the -a parameter with git commit to make it work somewhat similar to Mercurial.
Re:The Three Great Virtues of a Programmer: Laziness, Impati...
by carussell on Saturday June 27, 2015 @02:09PM
(#9790993)
I do use it, but that still qualifies as having to "futz[...] around with the index":
> -a, --all
> Tell the command to automatically stage files that have been modified and deleted, but new files you have not told Git about are not affected.
But this wasn't supposed to be a Git vs Mercurial post. It was supposed to be a GitHub vs sanity one, where Git-based solutions exist in the latter, too, which is why I mentioned use of Git outside of GitHub.
Have you used Git extensively outside of GitHub or done much with Mercurial? Patch-based/commit-only workflows are the right solution to, I dunno, probably 75% of fixes and don't get in the way like the aforementioned approach, which tends to be misapplied (read: used 100% of the time because GitHub demands it).
Commit-only workflows are very light on ritual, since it's got about the same overhead as leaving a two-line comment. Mercurial makes it even lighter, because you don't have to futz around with the index like you do in Git (so long as you're only changing an existing file and haven't introduced a new one).