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.

▲

chrishill89 3 days ago | parent | next [-]

> 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.

▲

adastra22 4 days ago | parent | prev [-]

That's a problem with your CI. You can configure it to test all commits which make up the PR.

▲

baq 4 days ago | parent [-]

My CI takes 20+ mins and costs meaningful $ per run. Not happening.

▲

adastra22 4 days ago | parent [-]

> That's a problem with your CI.

	▲	baq 4 days ago \| parent [-]
		Yes, but not in the way you think.