PRs should be small units of change. PRs should be the edit history. If your pro... | Hacker News

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

		Andys on Jan 12, 2023 \| parent \| context \| favorite \| on: Theory-building and why employee churn is lethal t... PRs should be small units of change. PRs should be the edit history. If your process involves one PR per feature this makes them large and unwieldy, hard to review, hard to test, and more likely hard to rollback.

hinkley on Jan 12, 2023 [–]

I commend your attempts to do CI and PRs at the same time, but most places have too high PR friction to make that work.

So it becomes a fight between the two.

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