ci: Don't require specific casing in PR title#4825
Merged
erikgb merged 1 commit intoweaveworks:mainfrom Mar 16, 2025
Merged
Conversation
erikgb
changed the title
erikgb
force-pushed
the
more-lenient-conventional-commit
branch
from
5c76e96 to
d89d19d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes
What changed?
This PR removes the strict requirement for an initial uppercase character in the (convention commit) PR title.
Why was this change made?
This will add less "fuzz" to the general contribution process, which has already annoyed me. 😉 But after discovering that release-please has a plugin to ensure nice release notes, even with mixed case subjects, I don't think this strict requirement is required anymore.
Relates to #4824.
How was this change implemented?
How did you validate the change?
Release notes
Documentation Changes