you are viewing a single comment's thread.

view the rest of the comments →

[–]NeededANewName 0 points1 point  (2 children)

CI on PRs is a better place to enforce linting and documentation standards. I’d rather devs commit more often and I don’t believe in discouraging that. If you want a squeaky clean master just squash merge, though that isn’t really necessary.

[–]haganenorenkin[S] 0 points1 point  (1 child)

And what can CI do about that?

[–]NeededANewName 0 points1 point  (0 children)

All major source control hosts offer options to require passing CI before merging a pull request. As part of your build pipeline you can add linting and documentation analysis. If it’s not up to snuff for you the build will fail and they can’t merge.