Repository navigation
Conversation
The check reads the pull request title and body, our comments, the commit messages in the pull request and the changed file names, using the checker taken from the base of a pull request. A second step runs the base corpus against the checker a pull request ships. The four scripts and register.yml are copies of the soqucoin-sdk files, so the guard is one file in every repository. register-corpora.yml runs the two head-side corpora, which the SDK runs inside its own test workflow. The check fails on this pull request by design: its base carries no checker, so there is no trusted copy to run. Make it required after this merges.
…ss-run job The shared files are copied from soqucoin-sdk, where the corpora run, and verified here by blob hash. register.yml fires on pull_request_target and the three comment events and loads the repository default branch on every trigger. The cross-run step, which runs the checker a pull request ships, moves to register-crossrun.yml on pull_request and stays advisory. register-lint.py follows the Link header, so a pull request longer than one page is read to the end.
|
The register check splits into two jobs, and this repository carries the change by copy.
The six shared files are byte-identical to
Reasoning and the two open items are on |
…the runner's own The step runs the checker a pull request ships. A run step is handed no repository token unless the workflow puts one in its environment and this one does not, so the check is against a later edit that adds one. The runner's cache and id-token service tokens are in every step, so the child process drops them. Two cases hold it: the step stops before any head code runs when a token is present, and the checker reads the runner token as absent. Removing the scrub makes the second read the value.
PUBLISH_GATE_OFF: pre-existing content.
1 participant
Installs the register check, which reads this repository's own published text: the pull request title and body, our comments, the commit messages in the pull request, and the changed file names. It runs on the platform, so it also covers a body edited in the web interface and a comment posted from a phone.
What is here
.github/workflows/register.yml.github/workflows/register-corpora.yml.github/scripts/register-lint.py.github/scripts/register-lint-selftest.py.github/scripts/register-pin-selftest.py.github/scripts/register-crossrun-selftest.pyThe scripts and
register.ymlare byte-identical to the soqucoin-sdk copies, so the guard is one file in every repository and the next copy is a copy.register-corpora.ymlis the one addition: the SDK runs those two corpora inside its existing test workflow, and this repository's CI is shaped differently.How it works
register.ymltakes the checker from the base of a pull request, so a pull request does not supply the checker that judges it. A second step runs the base's corpus against the checker a pull request ships, so the check reads on the checker as well as on the text.The check is red on this pull request, and that is the expected result
The base of this pull request carries no checker, so there is no trusted copy to run and the step fails closed. That is the designed behaviour for the change that installs it, and it clears on the next pull request.
For the same reason,
registershould be made a required check only after this has merged. Requiring it first leaves this pull request unmergeable.