gitlint: Add regex to ignore some long lines. #1509
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do, and why?
This was motivated by the failure of a CI run on #1494, where I added a URL to the commit body.
This does not resolve issues for all previous commits where the B1 rule of long lines in the body would fail, but will allow some obvious common cases to pass.
Inspired by jorisroovers/gitlint#255, this should cover at least lines starting with:
The downside to this rule is that the line numbering is apparently offset, based on the gitlint documentation.
(https://jorisroovers.com/gitlint/latest/ignoring_commits/)
This was tested manually on the last 1500 commits on
main
, and limits the number of gitlint errors as expected for URLs. No changes are noted for Co-authored-by: at this time.External discussion & connections
topic
How did you test this?
Self-review checklist for each commit