You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CI never validates main: ci.yaml has no push trigger, so a direct push lands uncheckedΒ #342
.github/workflows/ci.yaml triggers on pull requests only β there is no push trigger:
on:
pull_request:
branches: [main]
So nothing validates main itself. A commit that reaches main outside a pull request is never linted, type-checked, tested or built.
This is not hypothetical. Commit b1d6c664fc ("restore patched image tooling") landed directly on main β no (#N) suffix β and bumped lighthouse and puppeteer-core, rewriting the lockfile and growing the nested dependency tree from 2 entries to 26. No CI ran. The resulting breakage surfaced only indirectly, days later, as every open Dependabot PR failing all eight jobs at npm ci (#340).
Impact
A direct push can break main silently and stay broken until something unrelated trips over it β here, the entire dependency-update pipeline froze.
Automated health checks read default-branch CI runs. A repository with no push-triggered workflow produces no runs to fail, so it reports clean regardless of its actual state. The repository is invisible to breakage detection rather than healthy β the worse of the two, because nothing prompts a look.
Expected behaviour
CI runs against main as well as against pull requests, so the default branch carries a real, readable health signal.
Acceptance criteria
ci.yaml also triggers on push to main.
A run against main appears in the Actions tab and its conclusion reflects the branch's real state.
A concurrency group prevents a push run and a PR run for the same ref from duplicating work.
Rough size: small β a trigger block and a concurrency group.
Activity
chore: agent-claim #342 nonce=4250f2df588a7696c8291576f1a8b6e4