Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Clarify GITHUB_TOKEN access #973

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify GITHUB_TOKEN access #973

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,9 +89,14 @@ steps:
`release-please` requires a GitHub token to access the GitHub API. You configure this token via
the `token` configuration option.

For `release-please` to create pull requests, you will need to
[permit github actions to create an approve PRs](https://stackoverflow.com/questions/72376229).

> [!WARNING]
> If using GitHub Actions, you will need to specify a `token` for your workflows to run on
> Release Please's releases and PRs.
> Release Please's releases and PRs. See [the heading below](#other-actions-on-release-please-prs).

### Other Actions on Release Please PRs

By default, Release Please uses the built-in `GITHUB_TOKEN` secret. However, all resources created
by `release-please` (release tag or release pull request) will not trigger future GitHub actions workflows,
Expand Down