internal/

Package main ...

Package main A helper to run go test on CI with the right environment variables.

Package main is wand's image build script: it builds the two container images from the checkout it is run in, proves what the image Gate proves, and either keeps them on this machine or pushes them by digest for the release workflow to publish (spec #33, section 14; tickets #55 and #60).

Package main is the vulnerability scan of the Gate's linux/amd64 Go stable job, and the same command to run before pushing:

Package main is the lint step of go generate and of the generate Gate: the Node linters that internal/tools/package.json pins, then golangci-lint at the version internal/devutil pins (its formatters rewrite, its linters report), then upstream's Must-prefix rule and a clean git tree, so that a generator whose output drifted from the committed files fails here (spec #33, section 13).

Package main is the Nightly's issue opener: it reads the jobs of one workflow run and, for every job that went red, opens an issue keyed by that job's name or comments on the open one (spec #33, section 13; ticket #61):

Package main prints the three pins of lib/launcher/pins for the release workflow, which heads every release with them and appends them to versions.json, so no workflow parses Go source (ADR-0008, ADR-0009):

Package main is the version arithmetic and the release body of the release workflow: it validates the version it is given against the tags already published, appends that release's row to versions.json, and writes the head of the GitHub Release body — the three pins on the first line, and the Release preamble of docs/releases/<tag>.md under it when the release has one (spec #33, section 15; ADR-0008; ticket #60):

Package main applies the headlesslab repository settings bundle to one or more GitHub repositories through `gh api` and reports what it changed, so a new repository needs one command and drift is one re-run away:

Package main is the setup step of go generate and of the generate Gate: the Go modules, the Node tools of internal/tools/package.json from their lockfile (Node must be on PATH; golangci-lint needs no install, go run builds it at the pinned version), and the .dockerignore mirrored from .gitignore.

Package main It helps to launcher a transparent shell under the current shell with some extra environment variables that are required by wand testing.

Package main ...

Package main prints the Chrome the oldest milestone in the Support window resolves to, which is the browser the Support-window Nightly runs the suite on (spec #33, section 13; ADR-0008; ticket #61):

Package main moves every module in the graph as far forward as the Go floor allows, and says which ones could not come the whole way, which is what the Nightly's updated-graph job runs before it runs the suite (spec #33, section 13; ADR-0006; ticket #61):

Package main is the Zero leftover step every Tier 1 job ends with: it waits up to 30 s for the browsers a run launched to be gone, then fails on any chrome or chromium process still running and on anything still under launcher.DefaultUserDataDirPrefix, the directory the launcher makes its temporary user data directories in (spec #33, section 12; ticket #54).