Repository navigation
ci: fix the duplicated trigger key so the workflow runs again - #1026
Conversation
ci.yml has carried two 'on:' keys since April, which GitHub rejects as an invalid workflow, so neither lint nor the build check ran on any push or PR. Keep the build check (passes on stabilisation) and leave lint out until its 251-error backlog is cleared, so the fix does not turn every PR red.
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.
Tip: disable this comment in your organization's Code Review settings.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
|
What
.github/workflows/ci.ymlhas had twoon:keys since April (c94c695). GitHub rejects it as an invalid workflow, so every run since then fails instantly ("This run likely failed because of a workflow file issue") and neither lint nor the build check has run on any push or PR.bun install --frozen-lockfile+bun run type-check): it passes onstabilisationtoday.bun run lintreports 251 errors / 823 warnings onstabilisation, so enabling it would fail every PR. Clearing that backlog (161 errors are auto-fixable) is a separate change.Tests
stabilisation:bun install --frozen-lockfileclean,bun run type-checkexit 0,bun run lintexit 1 (251 errors).