3 ms·
> you're liberally using branches, right? Branches are cheap in Git Branches may be cheap in Git, but they're expensive in typical modern software eng. process
by burntoutfire 6y ago
> you're liberally using branches, right? Branches are cheap in Git
Branches may be cheap in Git, but they're expensive in typical modern software eng. process. For every branch, a PR must be opened, code must be reviewed, full test suite must be ran, the testers must ok that the change does not require extending the test suite, and only finally after the whole ordeal we're ok to merge. That's why I prefer my branches big and meaty.
- Zecc 6y ago> For every branch, a PR must be opened, code must be reviewed, full test suite must be ran, the testers must ok that the change does not require extending the test suite, and only finally after the whole ordeal we're ok to merge. Surely this isn't true for local branches on your machine? I hope you're not living under such a dystopia.
- bluefirebrand 6y agoBut this process is small and fast when your branches are small and fast. Code reviews length takes exponentially longer and misses way more when branches are "big and meaty"
- carlmr 6y agoIt should be small and fast, but depending on where you work it isn't. And trying to get a big corp to adapt to you is like trying to boil the ocean.
- tolbish 6y agoJust create the branch locally for your incremental changes and then when you are done, connect the remote repository to initiate the PR.