Skip to content

ci: pass PAT to release-please so its PRs trigger workflows#20

Merged
lxcong merged 1 commit intomainfrom
ci/release-please-pat
Apr 27, 2026
Merged

ci: pass PAT to release-please so its PRs trigger workflows#20
lxcong merged 1 commit intomainfrom
ci/release-please-pat

Conversation

@lxcong
Copy link
Copy Markdown
Contributor

@lxcong lxcong commented Apr 27, 2026

Summary

  • Pass RELEASE_PLEASE_TOKEN (PAT) to googleapis/release-please-action@v4 instead of relying on the default GITHUB_TOKEN.

Why

PRs created with the default GITHUB_TOKEN do not trigger other workflows (GitHub docs). Branch protection on main requires the commitlint check, but commitlint.yml runs on pull_request events — which never fire for release-please PRs. The result: every release PR (e.g. #19) stays mergeable_state: blocked forever.

Using a PAT makes release-please open PRs as a real user, so pull_request: opened fires and commitlint runs.

Test plan

  • This PR itself triggers commitlint (proves human-authored PRs are unaffected)
  • After merge, close+reopen chore(main): release 1.2.0 #19 to unblock the current 1.2.0 release
  • Next release-please PR opens with commitlint already running automatically

Without an explicit token, release-please uses the default GITHUB_TOKEN.
PRs created with GITHUB_TOKEN do not trigger other workflows, so the
required commitlint check never runs on release PRs and they stay
blocked by branch protection.

Use RELEASE_PLEASE_TOKEN (a PAT) so opened PRs trigger commitlint.
@lxcong lxcong merged commit 0073da2 into main Apr 27, 2026
1 check passed
@lxcong lxcong deleted the ci/release-please-pat branch April 27, 2026 14:19
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