4 ms·
idea looks nice, but can you share what's your workflow to push 90 commits/day? I understand each commit might have different size, but I am guessing your comm
by throwaw12 2mo ago
idea looks nice, but can you share what's your workflow to push 90 commits/day?
I understand each commit might have different size, but I am guessing your commits == Pull Request (because you need this constant merge queue to rebase, merge, test) and each are around 40-80 lines of code (additions and removals), and you are probably not reviewing the code because at this rate even if one commit takes 2 minutes to review we are talking about 3 hours of non stop code review.
if you are not reviewing each code, probably your commits are small items and 10-20 of them are a part of single PR, then how do you sustain working across multiple projects?
- funador 2mo agoDefinitely 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/ https://hola.career/) so I afford to a bit more loose than I would in professional capacity.