Skip to content

Make rbs validate a blocking CI check again - #1317

Open
apiology wants to merge 2 commits into
castwide:masterfrom
apiology:ci-continue-on-error-audit
Open

Make rbs validate a blocking CI check again#1317
apiology wants to merge 2 commits into
castwide:masterfrom
apiology:ci-continue-on-error-audit

Conversation

@apiology

Copy link
Copy Markdown
Contributor

rbs validate in the Linting workflow carries continue-on-error: true from #1200, marked # @todo Temporary, expect to revert in 0.60. 0.60 has since shipped through 0.60.3.

Unlike the other steps stubbed in that commit, this one passes — on master and on every recent PR run sampled, none of which contain Process completed with exit code. So removing the flag suppresses nothing and changes no outcome today; it only lets the check report what it finds from here on.

Out of scope: the solargraph typecheck --level strong flag is handled by #1240, the two rubocop_todo flags by #1260. The rest still exit non-zero and each needs its own fix.

This PR was written by Claude Code on behalf of @apiology.

`bundle exec rbs validate` was masked with `continue-on-error: true`
in 09be4a6 (castwide#1200) along with seven other steps,
marked "expect to revert in 0.60". 0.60.0 through 0.60.3 have shipped.

The step passes on every run sampled: the master push at 8fda633
and five recent pull-request runs. Nothing is being suppressed, so
the flag only hides the verdict of a check that already reports
accurately.

The other steps from that commit still exit non-zero and are left
alone.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CXmnT5gSB1PheL9UbiGEVA
apiology added a commit to apiology/solargraph that referenced this pull request Aug 19, 2026
@apiology
apiology marked this pull request as ready for review August 24, 2026 22:06
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.

1 participant