chore: attempt to force coveralls status - #398
Merged
Merged
Conversation
sighphyre
force-pushed
the
chore/patch-ci-the-return
branch
from
July 24, 2026 09:05
5df1708 to
fb6acf6
Compare
Coverage Report for CI Build 30081282972Coverage remained the same at 93.194%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
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
4 participants
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.
Posts the legacy coverage/coveralls commit status from CI after the Coveralls upload completes.
Coveralls is receiving coverage, but GitHub branch protection is still waiting forever for that required status context. This keeps the existing upload and explicitly reports success/failure for the required check.
Bit of a dirty hack but I just want coveralls to stop blocking my life