Skip to content

Conversation

@tcard
Copy link

@tcard tcard commented Dec 11, 2025

A failed CI doesn't necessarily mean the PR won't get merged. CI could be retried, or it could be non-blocking.

Add a --stop-on-failed-ci flag to skip the CI check, and rely only on the merged or closed status. Defaults to true for backwards-compatibility.

@tcard tcard requested a review from a team as a code owner December 11, 2025 17:48
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

),
},
&cli.BoolFlag{
Name: "stop-on-failed-ci",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this would be more clear if the flag were named something like continue-on-failed-ci or ignore-failed-ci which would default to false to preserve the existing behavior.

Closed: true,
CIStatus: github.CIStatusFailed,
},
allowFailedCI: true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of using a test-only field here, I think it makes more sense to directly set the prConfig field for the test scenario:

Suggested change
allowFailedCI: true,
continueOnFailedCI: false,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants