4 ms·
Seems equivalent to a git add -p # Review and stage git commit # Create commit git stash # Save uncommitted changes run_tests.sh # double-check git s
by sagarm 5y ago
Seems equivalent to a
git add -p # Review and stage
git commit # Create commit
git stash # Save uncommitted changes
run_tests.sh # double-check
git stash pop # or drop
I'll do something like occasionally, but mostly I just rely on the CI to double-check me.
- gfxgirl 5y agoYes, that is equivalent, except that you had to be aware of the staging area and its implications. CIs on large teams can't run fast enough to check every individual commit. They have to run them in bulk. So the CI will often not catch that of your 2 consecutive commits the first one breaks if the 2nd one fixes that break.
- sagarm 5y agoI've also worked on large teams, and for us every published version of every change within our project is automatically tested. If your CI is too expensive to run on every commit it probably needs optimization -- something I've done myself a few times. Not investing time or resources into making your CI fast and reliable is a false economy IMO.