-
Notifications
You must be signed in to change notification settings - Fork 4.5k
airbyte-ci: do the regression test status check on all PRs #42040
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
22a1ae2
to
8edbca1
Compare
8edbca1
to
0b6b05c
Compare
26c696d
to
b25dbb3
Compare
@@ -86,7 +86,7 @@ def do_regression_test_status_check_maybe(ctx: click.Context, status_check_name: | |||
run_url = ctx.obj["gha_workflow_run_url"] | |||
should_send = ctx.obj.get("ci_context") == consts.CIContext.PULL_REQUEST | |||
|
|||
if any( | |||
if is_automerge_pull_request(ctx.obj["pull_request"]) and any( |
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.
Don't we want the opposite behavior: when the pr has the automerge label we want to make the status check pass?
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
We were skipping the status check
success
call if the PR had no connector changes, but we should always send it.Also sends
success
if the PR is marked for auto-merge.