Hacker News new | ask | show | jobs
by baq 236 days ago
It’s mostly because pull requests are what is being tested in CI, not individual commits. Might as well squash as nobody wants to deal with untested in-between crap.

If you mean stacked PRs, yeah GitHub absolutely sucks. Gerrit a decade ago was a better experience.
2 comments
chrishill89 235 days ago
> Might as well squash as nobody wants to deal with untested in-between crap.

I would rather deal with nice and tidy but untested commits rather than a very well-tested but too monolithic squash. If you test the eventual merge then you have done no less testing than the squash case.

Old commits are read more than they are run.

link
adastra22 236 days ago
That's a problem with your CI. You can configure it to test all commits which make up the PR.
link
baq 236 days ago
My CI takes 20+ mins and costs meaningful $ per run. Not happening.
link
adastra22 236 days ago
> That's a problem with your CI.
link
baq 236 days ago
Yes, but not in the way you think.
link