feat: pr conventional commit title#55
Merged
chris11-taylor-nttd merged 31 commits intomainfrom Feb 6, 2026
Merged
Conversation
ben-vaughan-nttd
approved these changes
Jan 28, 2026
bryce-lynn-nttd
approved these changes
Feb 6, 2026
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
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.
Adds a workflow to enforce Conventional Commits in PR titles. This format is often used to drive automation in versioning and release notes. This is intended for use with a Squash Merge strategy, where the pull request's title lands on the commit history after it is merged.
Failure to provide a title in the Conventional Commits format will, by default, result in this comment being added to your PR:
Once the PR is correctly retitled, the comment is removed and the workflow will pass. You are recommended to enforce successful completion of this workflow via Rulesets, so that you have assurances that the commit added to your main branch meets the specification.
See the corresponding .md document for usage and configuration.