Skip to content

fix: grant pull-requests read permission to lint-pr-title workflow#736

Open
abelonogov-ld wants to merge 1 commit into
mainfrom
fix/lint-pr-title-permissions
Open

fix: grant pull-requests read permission to lint-pr-title workflow#736
abelonogov-ld wants to merge 1 commit into
mainfrom
fix/lint-pr-title-permissions

Conversation

@abelonogov-ld

@abelonogov-ld abelonogov-ld commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Summary

  • The reusable workflow launchdarkly/gh-actions/.github/workflows/lint-pr-title.yml@main requests pull-requests: read, but the caller job granted pull-requests: none, producing a startup failure on PRs (including the release-please PR, e.g. run 29060791953).
  • Grant the calling lint-pr-title job contents: read and pull-requests: read so the nested reusable workflow is allowed to run.

Test plan

  • lint-pr-title check runs successfully on this PR instead of hitting a startup failure.

Note

Low Risk
CI-only permission scope change with read-only access; no application or runtime behavior changes.

Overview
Fixes GitHub Actions startup failures on PRs for the lint-pr-title check by declaring job-level permissions on the caller.

The lint-pr-title job now sets contents: read and pull-requests: read before invoking launchdarkly/gh-actions/.github/workflows/lint-pr-title.yml@main. The reusable workflow expects pull-requests: read, but the caller previously left PR access at the default/none effective level, which blocked the nested workflow from running (including on release-please PRs).

Reviewed by Cursor Bugbot for commit 211c6d0. Bugbot is set up for automated code reviews on this repo. Configure here.

The reusable workflow launchdarkly/gh-actions lint-pr-title.yml requests
'pull-requests: read', but the caller granted 'pull-requests: none',
causing a startup failure on PRs (including release-please PRs). Grant the
required contents/pull-requests read permissions to the calling job.

Co-authored-by: Cursor <cursoragent@cursor.com>
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