-
-
Notifications
You must be signed in to change notification settings - Fork 18
ci: ensure the auto-created release-please action runs CI
#192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR ensures that the auto-created pull requests from the release-please action trigger CI workflows by switching from the default GITHUB_TOKEN to WORKFLOW_PUSH_BOT_TOKEN. This follows the same approach previously implemented in the CSS repository (eslint/css#330).
Key changes:
- Configures
release-please-actionto useWORKFLOW_PUSH_BOT_TOKENinstead of the defaultGITHUB_TOKEN - Removes unnecessary
contents: writeandpull-requests: writepermissions (granted by the custom token) - Minor formatting improvements with additional blank lines
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| release-please: | ||
| runs-on: ubuntu-latest | ||
| permissions: | ||
| contents: write |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as eslint/js#713 (comment).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated it in fb32a3b
Prerequisites checklist
What is the purpose of this pull request?
This PR follows up on eslint/css#330.
In this PR, I've ensured the auto-created
release-pleaseaction triggers CI.Problem
Currently, the auto-created PR from the
release-pleaseaction does not trigger CI, as shown below:#184
This can result in CI not running and may lead to issues like eslint/rewrite#308 if the check is missing.
Solution
I've used
secrets.WORKFLOW_PUSH_BOT_TOKENinstead of the defaultsecrets.GITHUB_TOKEN, following the same approach described in eslint/css#330.Also, the
permissionsfield forcontentsandpull-requestsis no longer necessary becausesecrets.WORKFLOW_PUSH_BOT_TOKENalready grants the required permissions, so I removed it.FYI: the
tokeninput reference: https://github.com/googleapis/release-please-action?tab=readme-ov-file#action-inputsTest
I've tested it in my forked repository (using
rewriterepository), and it works as expected:lumirlumir/fork-rewrite#9
What changes did you make? (Give an overview)
This PR follows up on eslint/css#330.
In this PR, I've ensured the auto-created
release-pleaseaction triggers CI.Related Issues
Ref: eslint/css#330
Is there anything you'd like reviewers to focus on?
N/A