ci: clarify PR title hints and version bump requirements - #267
Merged
Merged
Conversation
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.
The title reminder currently warns on valid maintenance titles such as
test:andci:, and its copyable examples includePATCH -/MINOR -/MAJOR -text that does not match the required commit format. Match<type>: descriptionfor all PRs, including scopes and breaking-change markers, and comment only when that format is missing. Correcting a title removes the reminder; updates and deletion are restricted to the marked GitHub Actions bot comment.Explain the major, minor, and patch requirements in both the reminder and CONTRIBUTING.md, with version examples, non-release types, and precedence across merged commits. Emphasize that
feat:alone is minor and breaking changes require!or aBREAKING CHANGE:footer. This matches cwms-python PR #321 without changing release calculation.Validation: 34 cases against the actual inline workflow script with mocked GitHub APIs passed; the full configured pre-commit suite (Black, isort, yamlfix, and generated ownership checks) passed; whitespace checks passed. The workflow runs with
pull_request_target, so the new live behavior takes effect after merge.