lxcong 0073da2c39 ci: pass PAT to release-please so its PRs trigger workflows (#20) ...

## 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](https://docs.github.com/en/actions/security-for-github-actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow)).
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 #19 to unblock the current 1.2.0 release
- [ ] Next release-please PR opens with `commitlint` already running
automatically

Co-authored-by: lxhtheresa <lxhtheresa@gmail.com>

2026-04-27 22:19:46 +08:00

..

ISSUE_TEMPLATE

chore: initial public release

2026-04-23 13:52:31 +08:00

workflows

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

2026-04-27 22:19:46 +08:00

PULL_REQUEST_TEMPLATE.md

chore: initial public release

2026-04-23 13:52:31 +08:00