4 ms·
Maybe this is what you're saying, but to have CI prevent the merging of feature branches that introduce new warnings? That's my favorite setup for introducing l
by code_biologist 3y ago
Maybe this is what you're saying, but to have CI prevent the merging of feature branches that introduce new warnings? That's my favorite setup for introducing lint or lint rules to a large codebase.
- derefr 3y agoYes, but no need for the added complexity of a delta of warnings against the base branch. The presumption here (given the GP comment) is that main has no warnings, since warnings are only allowed "during development", and should be cleaned up before production. So the CI only has to be intelligent enough to prevent merging (to main) of a branch with any warnings.