Skip to content

A license, a version, and a CI workflow shipped disabled - #19

Merged
AgentDudu merged 2 commits into
developfrom
chore/release-readiness
Nov 9, 2026
Merged

AgentDudu merged 2 commits into
developfrom
chore/release-readiness

Conversation

@AgentDudu

@AgentDudu AgentDudu commented Nov 9, 2026 •

Copy link
Copy Markdown
Owner

Nothing behavioural. Three things main needed:

License: MIT, holder Rafael D (the git identity on every commit), 2026 = first commit year. A public repo with no license file is all rights reserved by default on GitHub. MIT because every dependency here is permissive (uplot, vite, vitest, TypeScript).

Version 0.1.0.

CI workflow, shipped .disabled — and that is the interesting part of this PR. I wrote it, then ran it instead of assuming:

probe job result
install → typecheck → test:quick → build failure in 4 s, zero steps, no log
a single echo failure in 4 s, zero steps, no log
actions/checkout@v4 (moving tag) same
actions/checkout@<sha> (pinned) same
pnpm/action-setup@<sha> same

Job detail: runner_id: 0, runner_name: "", runner_group_name: ""; repo settings enabled: true, allowed_actions: all; self-hosted runners total_count: 0. A bare echo failing identically means no GitHub-hosted runner is ever assigned on this account — nothing to do with the workflow, the pins, pnpm or Node 24. So enabling it would post a red X on every push for a reason that is not the code. The file header and README record what was observed and where to look (billing spending limits → GitHub Actions runners); renaming it to ci.yml is the whole enabling step.

Every gate it would have run already exists and passes locally — 133 tests, tsc --noEmit, and a headless-Chrome end-to-end check including hash-equality proofs for share links and saves. None of them ran automatically before this, which is how a suite sat uncommitted for three rounds.

…out someone remembering

The project had no license (GitHub shows an unlicensed public repo as all-rights-reserved), no CI,
and no version. 133 tests, typecheck, and a Chrome end-to-end gate all existed and all passed -- and
all of them only ran when a human remembered to run them, which is how a suite can sit uncommitted for
three rounds without anyone noticing.

CI: install --frozen-lockfile, typecheck, test:quick and build on every push and pull request to
main/develop; the full pnpm test (the behaviour and determinism runs, minutes of ticks) gates a merge
rather than every commit on a pull request. browser-check stays out of CI on purpose -- it drives a
real headless Edge over CDP and that toolchain is not on a runner -- and the README now says so in
plain words instead of implying the app is fully covered.

Actions are pinned to commit SHAs and the workflow gets contents: read, per the CI linters'
advisories; the v4 tag each SHA came from is recorded in the file with the command to re-check it.

MIT, holder Rafael D (the git identity on every commit), 2026 -- the first commit's year.
…t goes red on every push is worse than none

Renamed to .github/workflows/ci.yml.disabled. Proven environmental: a probe workflow with four jobs --
one of them a single `echo` -- failed identically in ~4 s with runner_id=0, runner_name="", and no log
blob, so no GitHub-hosted runner is ever assigned to this account's jobs. Actions are enabled on the
repo (allowed_actions: all) and there are no self-hosted runners. The file header says what was
observed and where to look (billing spending limits -> GitHub Actions runners); the README says the
gates are run by hand today, which is the truth a stranger reading it needs.
@AgentDudu AgentDudu changed the title A license, CI, and a version A license, a version, and a CI workflow shipped disabled Nov 9, 2026
@AgentDudu
AgentDudu merged commit b653d47 into develop Nov 9, 2026
@AgentDudu
AgentDudu deleted the chore/release-readiness branch November 9, 2026 09:11
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.

1 participant