chore(ci): temporarily make CI non-blocking for backlog merge - #397
Merged
Conversation
The type check, tests and build now run with continue-on-error so a red result cannot block merging the backlog of open contributor PRs. The steps still execute and their output stays in the logs; only the merge gate is lifted. The workflow is intentionally kept rather than deleted: if a branch protection rule requires the "build" check, removing the workflow means the check never reports and merges would block permanently. To restore enforcement, delete the continue-on-error lines. Co-Authored-By: Claude Opus 5 <noreply@anthropic.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.
Lifts the CI merge gate so the backlog of open PRs can be merged manually, per maintainer request. To be restored once the pipeline is fixed.
What changed
Type check,TestandBuildnow carrycontinue-on-error: true. They still run and their output is still in the logs — only the gate is lifted. AReport statusstep surfaces the livetscerror count as an annotation, so the real state stays visible at a glance.Why the workflow is kept, not deleted
If a branch protection rule requires the
buildcheck, deleting the workflow means that check never reports and merges block permanently — the opposite of the goal. A check that runs and passes is what actually unblocks merging.To restore enforcement
Delete the four
continue-on-error: truelines.Note on the 25 open PRs
This does not make them mergeable. GitHub is rejecting those with
Pull Request has merge conflicts, which is a conflict block, not a check block — no CI change affects it. They need resolved conflicts, which is what #396 already contains.🤖 Generated with Claude Code