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

It'll still mess up CI, sadly.


No, it does not. CI never builds those broken commits because they never go outside of authors personal computer. Commit often, push when it's done and only push commits that work.


The only way they never go outside of the author's personal computer is if the author squashes (or discards!) them before pushing. Otherwise, they will go outside of the author's personal computer.

However, they will never be a head outside of the author's personal computer, because they are pushed along with later commits that fix the brokenness. CI only ever builds heads, so the existence of the broken commits doesn't matter.


You're right. What I had on my mind writing the previous post - don't push broken commits. :)


Not all CI only builds heads. Some build and test all commits.


Well, then it will mark them fixed in HEAD then


Why would CI ever run a build of more than one commit sent in the same push? Isn't the push atomic? (Certainly it's worked that way for me in practice).


Suppose you want to know, not just the fact that dev is failing, but why it's failing. The particular commit that caused it to fail.




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

Search: