Skip to content

ci: guard the branches this repo actually has - #8

Open
BryanZaneee wants to merge 1 commit into
developfrom
chore/5-ci-branches
Open

ci: guard the branches this repo actually has#8
BryanZaneee wants to merge 1 commit into
developfrom
chore/5-ci-branches

Conversation

@BryanZaneee

Copy link
Copy Markdown
Owner

Summary

branches: [main, master][master, develop] in the push trigger.

Why

main has never existed in this repo, so half that trigger was dead the day it was written. develop now receives every merge and was not guarded at all. Closes #5.

Changes

One line in .github/workflows/test.yml. pull_request: is unqualified and already covers PRs to any branch, so it needs no change.

Testing

The workflow running on this PR is the test. Node matrix stays 20/22/24 — it collapses to 24 in T0, where engines moves and the change is justified by type stripping rather than done speculatively here.

Checklist

  • Docs moved in the same commit as the code
  • Goldens unchanged
  • test/generic.test.mjs green
  • No new dependency
  • ROADMAP ledger row W5 → done
  • Nothing modelled is drawn as observed

ADR

  • An architectural decision changed
  • Not applicable

`main` has never existed here — the trunk is `master` — so half the
push trigger was dead the day it was written. `develop` is the branch
that now receives every merge, and it was not guarded at all.

Closes #5

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.

W5 — CI branches: master, develop

1 participant