chore(ci): use app token for API sync automerge#5603
Open
jgoux wants to merge 1 commit into
Open
Conversation
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@113c26eac9ebb22f8029901938a026f95029e346Preview package for commit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Updates the API Sync workflow so the auto-merge step uses the generated GitHub App token instead of the workflow-scoped token.
The workflow already grants the app token pull request and contents write permissions for creating the sync PR. Reusing that token for
gh pr merge --automatches the existing automated merge pattern and avoids the authorization failure caused by the workflow-levelcontents: readpermission on the built-in token.