testme-on-pr.sh now applies the documented public default GITEA_URL=git.autonomic.zone when the secret file intentionally contains no URL.
Why
The weekly upgrade run reached its first !testme verification and the helper stopped before posting because it required a value that every other CI helper defaults. The URL is public configuration, not a credential.
The failing live invocation reported only GITEA_URL: parameter null or not set; the remaining authenticated inputs were present.
No secrets are added or committed.
## What changed
`testme-on-pr.sh` now applies the documented public default `GITEA_URL=git.autonomic.zone` when the secret file intentionally contains no URL.
## Why
The weekly upgrade run reached its first `!testme` verification and the helper stopped before posting because it required a value that every other CI helper defaults. The URL is public configuration, not a credential.
## Evidence
- `bash -n .claude/skills/recipe-upgrade/testme-on-pr.sh` passes.
- The failing live invocation reported only `GITEA_URL: parameter null or not set`; the remaining authenticated inputs were present.
- No secrets are added or committed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What changed
testme-on-pr.shnow applies the documented public defaultGITEA_URL=git.autonomic.zonewhen the secret file intentionally contains no URL.Why
The weekly upgrade run reached its first
!testmeverification and the helper stopped before posting because it required a value that every other CI helper defaults. The URL is public configuration, not a credential.Evidence
bash -n .claude/skills/recipe-upgrade/testme-on-pr.shpasses.GITEA_URL: parameter null or not set; the remaining authenticated inputs were present.