Skip to content

fix: grant pr title lint status permission#76

Merged
Astro-Han merged 1 commit into
devfrom
fix/pr-title-lint-statuses
Apr 20, 2026
Merged

fix: grant pr title lint status permission#76
Astro-Han merged 1 commit into
devfrom
fix/pr-title-lint-statuses

Conversation

@Astro-Han

@Astro-Han Astro-Han commented Apr 20, 2026

Copy link
Copy Markdown
Owner

Summary

Add statuses: write to the pr-title-lint workflow permissions.

Why

pr-title-lint / lint-pr-title started failing on PR #73 even though the title itself is valid. The failing job log shows Resource not accessible by integration when amannn/action-semantic-pull-request tries to create a commit status from a pull_request_target run. The workflow currently grants contents: read and pull-requests: read, but not statuses: write.

Related Issue

None.

How To Verify

ruby -e 'require "yaml"; YAML.load_file(".github/workflows/pr-title-lint.yml")'

Manual checks:

  • Inspected the failed pr-title-lint / lint-pr-title run on PR fix: sync opencode tui compatibility slice #73 and confirmed the error is a missing commit-status permission, not a title-format violation.
  • Confirmed the workflow change is a single-line permission addition on the pull_request_target workflow.

Screenshots or Recordings

Not applicable.

Checklist

  • I ran the relevant verification steps
  • I tested visible changes manually when needed
  • I am targeting the dev branch

@gemini-code-assist

gemini-code-assist Bot commented Apr 20, 2026

Copy link
Copy Markdown

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@coderabbitai

coderabbitai Bot commented Apr 20, 2026

Copy link
Copy Markdown
Contributor

Warning

Rate limit exceeded

@Astro-Han has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 19 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 5 minutes and 19 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3a1f9a53-46b3-45f0-b17a-8b3b1112bc9a

📥 Commits

Reviewing files that changed from the base of the PR and between 5e39f90 and df6ed32.

📒 Files selected for processing (1)
  • .github/workflows/pr-title-lint.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/pr-title-lint-statuses

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

@Astro-Han Astro-Han merged commit 31172ea into dev Apr 20, 2026
9 of 11 checks passed
@Astro-Han Astro-Han mentioned this pull request Apr 20, 2026
Merged
3 tasks
@Astro-Han Astro-Han deleted the fix/pr-title-lint-statuses branch April 20, 2026 15:21
@Astro-Han Astro-Han added bug Something isn't working ci Continuous integration / GitHub Actions P1 High priority github_actions Pull requests that update GitHub Actions code and removed github_actions Pull requests that update GitHub Actions code labels Apr 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

bug Something isn't working ci Continuous integration / GitHub Actions P1 High priority

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Astro-Han