You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ci: a behavior-change gate: every PR says if it changes behavior for callers; yes needs '!' and an update note #197
0.6.0 changed a default that callers depend on (#171: nodkey run masks output when it is not on a terminal, and then stays the parent of the command). It was listed as a plain feature, so nobody who updated got a warning (#191). Before 1.0 a feature and a breaking change both bump the minor version, so the version number does not warn either.
What to build
.github/pull_request_template.md with one required line: Changes behavior for existing callers: yes or no. "Behavior" means defaults, stdout/stderr content, exit codes, signals, which process runs the command, config meaning, and time limits.
A CI check (extend .github/workflows/pr-title.yml or add a job) that fails when:
the line is missing or has another value;
the answer is yes, and the PR title has no ! (for example feat(run)!: …), or the PR does not add an "Updating from X" note in docs/updating.md;
Done in #208 (merged). #198 is done too, in #209 (merged).
Done when
The template (.github/pull_request_template.md) and the CI check (tools/prgate, run in the job "Conventional Commits title" of pr-title.yml) exist. tools/prgate/main_test.go tests each fail case. test: contract tests for how callers use nodkey run #209 was the first PR checked by it: prgate: ok.
docs/releasing.md describes the gate and "⚠ BREAKING CHANGES". The squash commit keeps the !, because the repository uses the PR title as the squash commit message (checked 2026-11-17).
Two points that differ from the issue text
To know that a PR adds an "Updating from X" section, the check also reads the diff of docs/updating.md (only that file) from the GitHub API, as text. It never runs or prints it, and it runs only code from main.
A new*_test.go file right in test/contract/, and a change to test/contract/README.md, do not count as a change in behavior. A new test pins behavior that callers already have. Without this, test: contract tests for how callers use nodkey run #209 (which only adds tests of today's behavior) would have needed !. Any other change there counts: a changed, removed or moved file, and any other new file (such as a go.mod or a file in testdata/).
The check is in a job that is already required, so no ruleset change is needed. The release PR of release-please and Dependabot PRs that change only dependency files need no answer line.
Activity
groupsky commentedon Nov 17, 2026
hq-jobs
nodkey-release-ci-1(runr-20261117-203018-cc7d)Done in #208 (merged). #198 is done too, in #209 (merged).
Done when
.github/pull_request_template.md) and the CI check (tools/prgate, run in the job "Conventional Commits title" ofpr-title.yml) exist.tools/prgate/main_test.gotests each fail case. test: contract tests for how callers use nodkey run #209 was the first PR checked by it:prgate: ok.docs/updating.mdhas the feat(run): mask fetched values by default; --no-mask turns it off #171 section ("Updating from 0.5.0 or older").docs/releasing.mddescribes the gate and "⚠ BREAKING CHANGES". The squash commit keeps the!, because the repository uses the PR title as the squash commit message (checked 2026-11-17).Two points that differ from the issue text
docs/updating.md(only that file) from the GitHub API, as text. It never runs or prints it, and it runs only code frommain.*_test.gofile right intest/contract/, and a change totest/contract/README.md, do not count as a change in behavior. A new test pins behavior that callers already have. Without this, test: contract tests for how callers use nodkey run #209 (which only adds tests of today's behavior) would have needed!. Any other change there counts: a changed, removed or moved file, and any other new file (such as ago.modor a file intestdata/).The check is in a job that is already required, so no ruleset change is needed. The release PR of release-please and Dependabot PRs that change only dependency files need no answer line.