Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

CI will usually only run the latest commit. Even if commit a, b, and c were all tested, the resulting commits a', b', and c' after rebase would usually only have the last one tested.


Since you shouldn't publish commits that weren't tested, this suggests you should publish only one commit at a time.

(Unless you think "works on my machine" is good enough testing. Sometimes it is.)


So rebase then force push a', wait for CI, push b', wait for CI, push c'? Personally I just squash on merge.


And if you care about each commit always passing all test you should change your CI config accordingly.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: