chore: install pdisc (frontmatter, INDEX, CI gate) #1
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/pdisc-install"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Rolls out progressive disclosure (orion/tasks#69) to this repo, per https://git.dmb.zone/torb/ops/issues/12 (child of orion/infra#689).
pdisc.py install: vendoredtools/pdisc/,.githooks/pre-commit,.forgejo/workflows/pdisc.yml(CI gate),.pdisc.yamlREADME.md, generatedINDEX.mdpython3 tools/pdisc/scripts/pdisc.py checkprintsokDocs and tooling files only; no runtime/source change, nothing to deploy.
Also:
ci / ciwas red on main (template.trb vs. the published nightly); the CI steps now checksrc tests examplesas a workaround, see the PR comment.CI red on
b59a466:ci / ci (pull_request)fails after 7s - not caused by this diff (docs/tooling only, no.trbor workflow change):cihas been red on main since842ed44and57b8930, last green on7341633.pdisc / pdiscis green. I could not read the job log with my token, so the cause is unknown (suspect thetorbinstall/check steps). Please fix main CI (separate PR or here); the next CI run on a green base brings me back for the review. No other findings so far.Review of
b59a466(docs/tooling only: pdisc install, README frontmatter, INDEX.md, CI gate).Checklist:
pdisc / pdiscgreen;ci / cired (see 1)..pdisc.yamland generated INDEX.md are consistent with the PR body; the pdisc check passes in CI.python3-yamlif missing.Findings:
ci / ciis red on this head (failing after 7s). It is not caused by this diff: the same check has been red on main since842ed44and57b8930(last green7341633), and this PR touches neither.trbfiles norci.yml. I cannot read the job log with my token, so the cause is unknown (suspect the torb install/format/check steps). Please fix main CI (separate PR, or here if you prefer) and re-run it on this head; I will then approve and merge without further findings.Non-blocking:
tools/pdisc/assets/frontmatter.schema.json$idpoints at an internal host (git.dmb.zone) in a public repo. Consider having the install step rewrite or drop the$idfor public repos.Fixed the red
ci / ciin96c80f8(cause found by reproducing the job locally with nightly-20260929):template.trb(added in842ed44, read statically bytorb new) is checked as TorbScript source by the published nightly and fails withCannot find replace/drop/title/...(5 problems).torb format --check .is fine. The CI steps now checksrc tests examples(torb check src tests examples,torb test tests,torb doc --check src examples) in both.forgejoand.githubci.yml, with a comment to go back to.once a nightly skipstemplate.trb. Locally: check 3 files no problems, tests 2 passed. The real fix is on the toolchain side (skiptemplate.trb); this is a workaround.Not done: the
$idin the vendoredfrontmatter.schema.jsoncomes from the upstream pdisc asset; changing it in the vendored copy would drift from the source, so that is a follow-up in the pdisc install step.Re-requesting review.
Re-review of
96c80f8(earlier finding 1 + the lines changed since).Checklist:
ci / ciandpdisc / pdiscboth green on exactly this head. Earlier blocker 1 (redci / ci) is resolved.b59a466is the CI steps in.forgejo/workflows/ci.ymland.github/workflows/ci.yml:torb check src tests examples,torb test tests,torb doc --check src examples.torb format --check .still covers everything. The workaround and its exit condition (go back to.once a nightly skipstemplate.trb) are documented in a comment and in the PR.Non-blocking:
tools/pdisc/assets/frontmatter.schema.json$idstill points at an internal host. Your rationale (vendored copy should not drift from upstream) is accepted; the follow-up in the pdisc install step is the right place.torb checkno longer covers files outsidesrc tests examples; track the toolchain-side fix so the workaround gets reverted.Approved on
96c80f8, but the merge failed:POST /pulls/1/merge(Do=rebase, head_commit_id=96c80f8) returned 405 "User not allowed to merge PR". Theargusaccount is not on the merge whitelist (or lacks write) formainin torb/package-template. Needed: addargusto the merge whitelist, or merge manually; the review is APPROVED and CI is green.