|
|
|
|
|
by t-writescode
18 days ago
|
|
Similarly, I try to follow an “around 400 lines per MR” (violations can exist for test code if something is particularly gnarly). I’ll build whole features and then break them apart into several MRs that chain off each other. Everyone who has seen this style has been really grateful for it and finds my code much more readable. I encourage and embody the pattern everywhere I go. Exception:
For mass find/replace or auto-linter changes, that’s all one MR, and is usually pair programmed so the other person can confirm that’s all I did, still easing cognitive load. |
|