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

It hasn't been an issue in my experience at $DAY_JOB, but for us all commits must pass CI and not just the tip of whatever branch was just pushed. So branches with partial commits that fail CI cannot be merged. So if you commit an incorrect partial commit, you either squash it into a commit that does pass CI (usually the next one forward) or you rebase and edit the failed commit and fix it and force push your branch and run CI on the whole changeset again.




If you push a branch with many commits, does it run CI on each commit? In sequence or with some parallelism?

It runs on the last commit with the idea that it will all be squashed at merge. Are you worried about reverting some commits but not all?

That depends on the forge and the configuration of the forge. See the parent of the comment you replied to. Not everyone uses squash merge.

That's the normal setup, but the parent comment made it sound like theirs would build every commit?



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

Search: