What happened
The shared agent-loop mechanism repo Netis/agent-ops has been renamed to Netis/olympus.
GitHub redirects git clone/fetch/push, web links, and the REST API from the old name — but GitHub Actions does NOT redirect uses: references. From GitHub's own docs ("renaming a repository"):
GitHub will not redirect calls to an action hosted by a renamed repository. Any workflow that uses that action will fail with the error repository not found.
So Heron's 5 wrapper workflows that pin uses: Netis/agent-ops/... now fail to resolve on their next trigger.
Fix — change the owner segment only, on main
Repoint the 5 uses: lines from Netis/agent-ops → Netis/olympus. Keep the @tag exactly as-is (the tags travelled with the repo, so Netis/olympus@v0.2.0 / @v0.3.1 resolve to the same frozen content):
| File |
Line |
Change to |
.github/workflows/guard.yml |
34 |
uses: Netis/olympus/.github/workflows/guard.yml@v0.2.0 |
.github/workflows/issue-implement.yml |
40 |
uses: Netis/olympus/.github/workflows/implement.yml@v0.2.0 |
.github/workflows/issue-triage.yml |
27 |
uses: Netis/olympus/.github/workflows/triage.yml@v0.2.0 |
.github/workflows/pr-revise.yml |
33 |
uses: Netis/olympus/.github/workflows/revise.yml@v0.2.0 |
.github/workflows/pr-review.yml |
42 |
uses: Netis/olympus/.github/workflows/review.yml@v0.3.1 |
Do NOT change (yet)
These pinned tags predate the Olympus rebrand, so their frozen code still expects the old names. Changing them now would break the loop:
- The
@v0.2.0 / @v0.3.1 pins — stay on the same tags.
- The
agent_ops_ref: input name in each wrapper — the frozen reusable workflows read that input, not olympus_ref.
.agent-ops.json — the frozen code loads .agent-ops.json, not .olympus.json.
Rename .agent-ops.json → .olympus.json and switch the input to olympus_ref: only when you later bump to a post-rename Olympus tag (≥ the first tag cut after the rebrand). That is a separate, deliberate upgrade.
Why the inner checkout still works
Inside those frozen tags, the reusable workflow does actions/checkout with repository: Netis/agent-ops hardcoded. That is a git operation, which does follow the rename redirect — so it keeps cloning fine. Only the outer uses: resolution (which doesn't redirect) needs the owner change. Net: a 5-line, owner-segment-only edit fully restores the loop.
Expected symptom until merged
The issue-triage.yml run triggered by this very issue will fail with repository not found — that is the concrete manifestation of the breakage above, not a separate bug. It clears once this fix lands on main.
Verify after merge
Trigger a cheap path and confirm the reusable workflow resolves, e.g. open a no-op PR (fires guard.yml) or dispatch pr-review-probe.yml.
Hard rule
Never create a new repo at Netis/agent-ops. It would shadow the git/web/API redirect and break the inner checkout too.
Context: Netis/olympus migration guide — docs/migration.md.
What happened
The shared agent-loop mechanism repo
Netis/agent-opshas been renamed toNetis/olympus.GitHub redirects
git clone/fetch/push, web links, and the REST API from the old name — but GitHub Actions does NOT redirectuses:references. From GitHub's own docs ("renaming a repository"):So Heron's 5 wrapper workflows that pin
uses: Netis/agent-ops/...now fail to resolve on their next trigger.Fix — change the owner segment only, on
mainRepoint the 5
uses:lines fromNetis/agent-ops→Netis/olympus. Keep the@tagexactly as-is (the tags travelled with the repo, soNetis/olympus@v0.2.0/@v0.3.1resolve to the same frozen content):.github/workflows/guard.ymluses: Netis/olympus/.github/workflows/guard.yml@v0.2.0.github/workflows/issue-implement.ymluses: Netis/olympus/.github/workflows/implement.yml@v0.2.0.github/workflows/issue-triage.ymluses: Netis/olympus/.github/workflows/triage.yml@v0.2.0.github/workflows/pr-revise.ymluses: Netis/olympus/.github/workflows/revise.yml@v0.2.0.github/workflows/pr-review.ymluses: Netis/olympus/.github/workflows/review.yml@v0.3.1Do NOT change (yet)
These pinned tags predate the Olympus rebrand, so their frozen code still expects the old names. Changing them now would break the loop:
@v0.2.0/@v0.3.1pins — stay on the same tags.agent_ops_ref:input name in each wrapper — the frozen reusable workflows read that input, notolympus_ref..agent-ops.json— the frozen code loads.agent-ops.json, not.olympus.json.Rename
.agent-ops.json→.olympus.jsonand switch the input toolympus_ref:only when you later bump to a post-rename Olympus tag (≥ the first tag cut after the rebrand). That is a separate, deliberate upgrade.Why the inner checkout still works
Inside those frozen tags, the reusable workflow does
actions/checkoutwithrepository: Netis/agent-opshardcoded. That is a git operation, which does follow the rename redirect — so it keeps cloning fine. Only the outeruses:resolution (which doesn't redirect) needs the owner change. Net: a 5-line, owner-segment-only edit fully restores the loop.Expected symptom until merged
The
issue-triage.ymlrun triggered by this very issue will fail withrepository not found— that is the concrete manifestation of the breakage above, not a separate bug. It clears once this fix lands onmain.Verify after merge
Trigger a cheap path and confirm the reusable workflow resolves, e.g. open a no-op PR (fires
guard.yml) or dispatchpr-review-probe.yml.Hard rule
Never create a new repo at
Netis/agent-ops. It would shadow the git/web/API redirect and break the inner checkout too.Context:
Netis/olympusmigration guide —docs/migration.md.