Allow auto-merge for PRs opened by the Sepia onboarding app - #646
Merged
Conversation
GitHub Apps report author_association NONE, so PRs from sepia-lab-onboarding-app[bot] passed validation but were never auto-merged. Allow that bot explicitly; the head-repo check already guarantees the branch was pushed by something with write access. Signed-off-by: David Galloway <david.galloway@ibm.com>
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.
Summary
sepia-lab-onboarding-app[bot]passed thevalidatejob butautomergewas skipped, because GitHub Apps haveauthor_association: NONEand weren't in the OWNER/MEMBER/COLLABORATOR allowlist.head.repo.full_name == github.repositorycheck already guarantees the branch was pushed by something with write access to this repo, so this doesn't widen who can trigger a merge.After merging
#644 and #645 need a new
pull_requestevent (close/reopen) to pick up the updated workflow. #366 predates the workflow and also needs a close/reopen; #15 has a deleted fork and can't be validated by CI.