Skip to content

ci

Defines one Verify command from checks the repository already has, and creates or aligns a matching GitHub workflow.

/ci
  • Verify is the recipe — the project’s own checks, in order: typecheck, tests, build.
  • GitHub Actions is the worker — it runs that same recipe on pull requests and default-branch pushes.
  • A GitHub ruleset is the lock — a separate remote setting you make yourself.
  • A pre-push hook is the early warning — opt-in, defaults to no, and git push --no-verify bypasses it.
  • It never invents a test runner, coverage target, browser suite, security scan, or version matrix to fill the workflow.
  • Existing CI is preserved; changing it needs your approval.
  • It grants only contents: read by default.
  • It never pushes or changes a remote ruleset.
  • Until the workflow runs on GitHub, the setup is described as prepared locally, not CI verified.