ci: add conventional commit enforcement for PR titles#200
Open
ci: add conventional commit enforcement for PR titles#200
Conversation
Uses amannn/action-semantic-pull-request to validate PR titles follow conventional commit format before merging to main, matching the setup in the SGP repository.
declan-scale
approved these changes
Apr 16, 2026
Collaborator
declan-scale
left a comment
There was a problem hiding this comment.
Can we add a quick blurb to the CONTRIBUTING.md
Author
done |
declan-scale
approved these changes
Apr 16, 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.
Summary
lint-pr.yaml) that validates PR titles follow Conventional Commits format before merging to mainamannn/[email protected](pinned to SHA), matching the existing setup in the SGP and agentex (private) repositoriesfeat,fix,docs,style,refactor,test,chore,ci,build,perf,revertskip-conventional-commit-checklabel escape hatch for bot/automated PRsNote
After merging, add
Validate PR title (Conventional Commits)as a required status check in the branch protection rules formain(Settings → Branches →mainrule → Require status checks). Without this, the workflow will run but won't block non-compliant PRs.Test plan
Greptile Summary
This PR adds a GitHub Actions workflow (
lint-pr.yaml) to enforce Conventional Commits formatting on PR titles, and updatesCONTRIBUTING.mdto document the new requirement. The workflow is well-structured: it uses a SHA-pinned action, declares minimal permissions (statuses: write,pull-requests: read), covers all relevant PR trigger events, and provides a label-based escape hatch for bot PRs.Confidence Score: 5/5
Safe to merge — clean CI addition with no logic issues, correct permissions, and good documentation.
Both changed files are straightforward: a new workflow with a SHA-pinned action and minimal permissions, and updated docs. No P0 or P1 findings. The one nuance (CONTRIBUTING.md states the check will block merges before branch protection is configured) is acknowledged in the PR description and is P2 at most.
No files require special attention.
Important Files Changed
Sequence Diagram
sequenceDiagram participant Dev as Developer participant GH as GitHub participant WF as lint-pr workflow participant Action as action-semantic-pull-request Dev->>GH: Open / Edit / Sync PR GH->>WF: Trigger (pull_request event) WF->>Action: Run with GITHUB_TOKEN + PR title alt Title matches conventional commit format Action->>GH: Post ✅ status check (pass) else Title does NOT match Action->>GH: Post ❌ status check (fail) end alt PR has skip-conventional-commit-check label Action->>GH: Skip check entirely endReviews (2): Last reviewed commit: "docs: update CONTRIBUTING.md with conven..." | Re-trigger Greptile