Repository navigation
Allow completed Codecov failures during automerge - #16
Merged
Merged
Conversation
Signed-off-by: Tim Paine <3105306+timkpaine@users.noreply.github.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
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.
Completed
codecov/patchandcodecov/projectfailures currently block otherwise passing pull requests. Add an exact-name allowlist for check runs and legacy commit statuses so these coverage results are non-blocking after they finish.Pending Codecov results and every other unsuccessful check still block automerge. GitHub continues to enforce required repository checks and merge policies. Update README and landing-page behavior descriptions.
Type checking, formatting, all 70 tests, and the Worker dry-run build pass. Regression tests cover Codecov failures, pending results, failed builds, and names outside the allowlist.