Skip to content

fix(release): the probe declares its commands before it doctors #39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
indykish merged 1 commit into from
Sep 8, 2026
Merged

fix(release): the probe declares its commands before it doctors #39

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,14 @@ jobs:
bash /tmp/release-probe/package/bin/orly init
test -f AGENTS.orly.md || { echo "✗ orly's rules did not land"; exit 1; }
test -f AGENTS.md || { echo "✗ the repository's own file did not land"; exit 1; }
# `init` seeds commands by reading a Makefile and package.json scripts,
# and this probe repository is one Go file — so it seeds none, and
# `doctor` refuses an incomplete setup rather than passing a repository
# that declares no way to check itself. Declaring them here is the
# completion a real repository performs after init, and it is what the
# probe is actually for: proving the packed tarball installs, renders,
# and doctors clean once its setup is finished.
node -e 'const f=".oracle/orly.json",fs=require("fs"),c=JSON.parse(fs.readFileSync(f,"utf8"));c.commands={...c.commands,conform:[["true"]],"verify.unit":[["true"]]};fs.writeFileSync(f,JSON.stringify(c,null,2)+"\n")'
bash /tmp/release-probe/package/bin/orly doctor
echo "✓ the packed tarball installs and doctors clean"

Expand Down
Loading