Definitely not reviewing the code when 90 commits go in a day :)
I have local test suite of unit / arch / e2e / build / lint / tsc when it merges to dev. Then the same suite runs on a merge to main which pushes to prod. I have post main-push e2e that checks for regressions and automatically rolls back.
Each suite run takes 3-4 minutes so I can usually push through 15 or so commits an hour fully tested and cleanly.
I do not use PRs with this workflow, and if something breaks I add tests to prevent it happening again rather than altering the setup.
Most of the commits are for a side project (https://hola.career/) so I afford to a bit more loose than I would in professional capacity.
I have local test suite of unit / arch / e2e / build / lint / tsc when it merges to dev. Then the same suite runs on a merge to main which pushes to prod. I have post main-push e2e that checks for regressions and automatically rolls back.
Each suite run takes 3-4 minutes so I can usually push through 15 or so commits an hour fully tested and cleanly.
I do not use PRs with this workflow, and if something breaks I add tests to prevent it happening again rather than altering the setup.
Most of the commits are for a side project (https://hola.career/) so I afford to a bit more loose than I would in professional capacity.