Skip to content

ci: validate conventional pull request titles - #164

Merged
athal7 merged 1 commit into
mainfrom
ci/conventional-title
Aug 17, 2026
Merged

ci: validate conventional pull request titles#164
athal7 merged 1 commit into
mainfrom
ci/conventional-title

Conversation

@athal7

@athal7 athal7 commented Aug 17, 2026

Copy link
Copy Markdown
Owner

Adds Conventional Commit validation for pull request titles.

@coderabbitai

coderabbitai Bot commented Aug 17, 2026

Copy link
Copy Markdown

Review Change Stack

Walkthrough

Added a GitHub Actions workflow for pull request title validation. The workflow runs when a pull request opens, changes, reopens, or becomes ready for review. It accepts supported commit types, optional scopes and breaking-change markers, and a required description. Invalid titles print an error and fail the workflow.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly identifies the CI change that validates pull request titles against Conventional Commit formatting.
Description check ✅ Passed The description directly explains that the pull request adds Conventional Commit validation for pull request titles.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a4da6327-7b0b-463e-af53-d3071b15bbfe

📥 Commits

Reviewing files that changed from the base of the PR and between c799710 and 3839f14.

📒 Files selected for processing (1)
  • .github/workflows/conventional-title.yml

Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review.

Comment on lines +7 to +8
permissions:
contents: read

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -eu

file=".github/workflows/conventional-title.yml"

if [ ! -f "$file" ]; then
  printf 'missing: %s\n' "$file"
  exit 0
fi

printf '%s\n' '--- workflow ---'
cat -n "$file"

printf '%s\n' '--- related token and permission references ---'
rg -n -i 'permissions|GITHUB_TOKEN|github\.event|pull_request|checkout|github api|curl|gh ' .github/workflows "$file" 2>/dev/null || true

printf '%s\n' '--- workflow files ---'
git ls-files '.github/workflows/*'

Repository: athal7/opencode-pilot

Length of output: 1864


Remove the unused contents permission.

This workflow only reads github.event.pull_request.title. Set workflow permissions to {}. Add a specific permission only if a later step requires it.

Proposed fix
 permissions:
-  contents: read
+  {}
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
permissions:
contents: read
permissions:
{}

@athal7
athal7 marked this pull request as ready for review August 17, 2026 19:53
@athal7
athal7 merged commit bea4f4a into main Aug 17, 2026
8 checks passed
@athal7
athal7 deleted the ci/conventional-title branch August 17, 2026 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant