chore: use GITHUB_TOKEN
to create sync PRs
#3360
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We were using the same token to create and approve the sync PRs, leading to
This isn't an issue for https://github.com/openedx/paragon/blob/release-23.x/.github/workflows/analyze-dependents.yml, which uses https://github.com/peter-evans/create-pull-request as opposed to https://github.com/TreTuna/sync-branches
https://github.com/peter-evans/create-pull-request has token as optional, and has the default documented as
GITHUB_TOKEN
This PR updates the sync workflow to create PRs using
secrets.GITHUB_TOKEN
, while keeping the approval token the same.Deploy Preview
Include a direct link to your changes in this PR's deploy preview here (e.g., a specific component page).
Merge Checklist
example
app?Post-merge Checklist