Skip to content
Central verification

Central verification (core/ci)

Every repository FORGE creates is verified centrally, by Runink TIDE, and the verdict is reported as one commit status, core/ci. This is verification, not a deploy pipeline: a green core/ci means TIDE’s verification passed.

No per-repository CI

Every repository FORGE creates (topic forged) carries no CI of its own and no App credentials. TIDE verifies it centrally. Do not add a workflow or a key to a forged repository. A repository is covered the moment it is tagged forged.

The flow

The sweep finds unverified commits

A sweep runs every 10 minutes. It lists the org’s repositories with /orgs/{org}/repos, not search: the search index lags, and a repository forged a minute ago is exactly the one someone is waiting on. It keeps every repository tagged forged, and skips archived and disabled ones.

For each target it collects the default-branch head first, then each open PR head. It picks the first SHA that has no core/ci status, or whose core/ci status has been pending for more than 90 minutes.

It claims, then dispatches

Before dispatching, it sets core/ci = pending with the description “queued for TIDE verification”. The claim comes first, so the next sweep skips the commit even if this run dies. It then starts verification in TIDE with {repo, sha, ref, kind}. The GitHub App reports through a commit status, because it needs only statuses: write for that.

TIDE verifies

The verification run:

  • validates the target (org/<name> and a 40-hex SHA);
  • mints an App token scoped to the target only;
  • re-derives the profile from the repo itself. The payload’s kind is not trusted;
  • refuses anything that is public, or that is not tagged forged;
  • sets core/ci to “TIDE verification running (<kind>)”;
  • checks out the SHA with persist-credentials: false, and runs the profile’s checks. No step that runs the target’s code has a token in its environment.

See Verification profiles.

It closes core/ci

A final step under always() mints a fresh token and posts the verdict. A cancelled or timed-out run therefore still closes its status, as error.

Throughput and safety rules

  • One verification per sweep. Verifications run one at a time, and the sweep starts none while one is already waiting. That gives at most six verifications an hour.
  • Default-branch heads first. They are what FORGE shows. A PR head waits behind every unverified default branch.
  • Public repositories and fork PRs are never dispatched. Verification builds and runs the target’s code on a self-hosted runner. Verification also refuses a public repository started by hand: "… is public — its code is never built on a self-hosted runner".
  • Stale pending recovers itself. A verification times out at 45 minutes and waits behind at most one running verification. A pending status older than 90 minutes therefore has no run behind it and is started again.
  • It never merges, pushes or comments. It only checks, and posts statuses.

The status contract

FORGE reads this. Do not deviate.

FieldMeaning
contextcore/ci, on the verified commit
pendingqueued (by the sweep) or running
successevery check of the profile passed
failurea check failed, including “Nothing to verify yet” for an empty pipeline
errorthe infrastructure could not run the checks: token, checkout, a missing toolchain, or a cancelled or timed-out run
target_urlthe verification run that decided it
descriptionat most 140 characters, and says why

Success descriptions per profile:

Profilecore/ci success description
webgo build/vet/test and npm ci/build passed
pipeline<n> pipeline file(s) parse as TOML; go build/vet/test passed over <p> package(s), or …; no Go package

Projects with forge.yaml: one status per lane

When a forged repository carries forge.yaml, the topic profile is not run. forgecheck manifest, then forgecheck lanes, then forgecheck aggregate (under always()) run instead, and post:

  • core/ci/<lane id> per lane, with the same states and meanings as core/ci. A lane with nothing to check is failure with a description starting Nothing to verify yet. Every lane context goes pending (“TIDE verification running”) as soon as the manifest is read.
  • core/ci, the aggregate, set to “TIDE verification running (N components, forge.yaml)” while running, and then:
ConditionStateDescription
any lane errorerrorN/M components could not be verified — <id>: <why>
any real lane failurefailureN/M components failed — <id>: <why>
every lane has nothing to verifyfailureNothing to verify yet: no component has code yet
otherwisesuccessP/M components verified[, E with nothing to verify yet]

A lane with no recorded result (a cancel or timeout) closes as error: “verification did not complete — cancelled or timed out”. An invalid manifest posts core/ci = failure with forge.yaml is invalid: <first reason> and no per-lane status. Repositories without forge.yaml are verified by their profile.

Who reads core/ci

  • FORGE, for its “CI build” stage. This is FORGE’s own reading of the same fact. For every CI agent, see CI workflows.