-
Notifications
You must be signed in to change notification settings - Fork 132
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.
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
fix(owl-bot): OwlBot to report a skip in pull request checks #5643
Conversation
OwlBot postprocessor has stopped running the script since googleapis#5587. Many repositories mark the postprocessor check as required. This change reports the check status as success with a message that indicates the execution was skipped.
"packages-owl-bot-test (repo-automation-bots) Failing after 1s — Summary" says:
|
All checks have passed |
@@ -615,14 +615,6 @@ const runPostProcessor = async ( | |||
logger: GCFLogger, | |||
breakLoop = true | |||
) => { | |||
// If the pull request is from a fork and not from allowlist, skip. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moving this logic after the declaration of createCheck
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chingor13 PTAL
text: 'Ignored by Owl Bot because the pull request was created from a fork. See go/owlbot-skip-forks.', | ||
summary: | ||
'Ignored by Owl Bot because the pull request was created from a fork', | ||
conclusion: 'skipped', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now it's skipped.
b/385183332. After #5587 and before this change, the post processor checks were silently skipped and those repositories that mark it as required cannot merge pull requests from external contributors.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #<issue_number_goes_here> 🦕