ci: auto approve API sync PRs#5756
Open
jgoux wants to merge 1 commit into
Open
Conversation
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@288c519093c70e4606dae4145873df3a86d2e41dPreview 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.
Follows up on #5753 by letting API sync PRs satisfy the approval requirement automatically.
This adds a dedicated approval step after the generated API sync PR is created. The step uses the shared account PAT stored in
AUTO_APPROVE_PR_PAT, while the existing GitHub App token continues to own PR creation and auto-merge setup.