ci: add commitlint workflow for PR commit messages - #4902
Open
ginglis13 wants to merge 1 commit into
Open
Conversation
Signed-off-by: Gavin Inglis <giinglis@amazon.com>
vyaghras
approved these changes
Jul 30, 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
2 participants
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.
Issue number:
n/a
Description of changes:
Add linting to commit messages for this repo. We've had some churn (and misses) the last few weeks on commit style, so let's enforce it via CI. The linting checks for
scope: messagestyle commits. This is slightly different than conventional commits, which are more the formfix(scope): messageorchore(scope): message, but the linting is based on our own conventions and commit history.Testing done:
Ran locally against last 50 commits. Only latest commit 0cef809 failed because it is missing a colon.
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.