Conversation
The publish step runs inside the build job, so any Coveralls error fails the build: fail-fast cancels the rest of the matrix and the required `ci-gate` goes red. A Coveralls 500 did exactly that on 2026-09-28 with all 419 tests passing, and a 422 did it on #185. The `coverage/coveralls` status was never a required check, but the publish step's exit code effectively made it one. continue-on-error keeps coverage reporting informational. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Folded into #190 at the author's request. |
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.
The Coveralls publish step runs inside the build job, so any Coveralls error fails
the build — fail-fast cancels the rest of the matrix and the required
ci-gategoes red. Coverage reporting was effectively a merge gate even though the
coverage/coverallsstatus was never a required check.It has blocked merges twice with every test passing:
500 Internal Server Error(run)422 Unprocessable Entitycontinue-on-error: trueon the publish step. A Coveralls failure now shows as awarning on that step while the job, and
ci-gate, still pass.🤖 Generated with Claude Code