I like the 500 lines rule. I would be interested if that could be incorporated as an automated rule in a devops setting - with the ability to override of course. It would really help devs to consider the scope of what they are working on when they know they are going to need to defend any huge changes.
Yeah, that's an interesting idea. I bet someone could whip up a one-liner with diffstat for a PR that could fail a CI build if the branch was too big. Overriding that behavior would be the hard part though.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I like the 500 lines rule. I would be interested if that could be incorporated as an automated rule in a devops setting - with the ability to override of course. It would really help devs to consider the scope of what they are working on when they know they are going to need to defend any huge changes.
Yeah, that's an interesting idea. I bet someone could whip up a one-liner with
diffstatfor a PR that could fail a CI build if the branch was too big. Overriding that behavior would be the hard part though.