ci: repoint agent-loop wrappers to Netis/olympus (agent-ops renamed)#165
Merged
Conversation
The shared mechanism repo Netis/agent-ops was renamed to Netis/olympus. GitHub Actions does NOT follow repo renames when resolving `uses:` (git/web/API do redirect, but the Actions resolver does not), so the five wrappers were failing with "repository not found". Change the `uses:` owner segment only. The @tag is unchanged (tags travelled with the repo, so Netis/olympus@v0.2.0 / @v0.3.1 is the same frozen code), and `agent_ops_ref` + `.agent-ops.json` stay as-is — that frozen pre-rename code reads them. The reusable workflow's inner actions/checkout of the old path keeps working via the git-level redirect. Closes #164. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the breakage from renaming the shared mechanism repo
Netis/agent-ops→Netis/olympus.Why
GitHub Actions does not follow repository renames when resolving
uses:— per GitHub's docs the run fails withrepository not found. (git/web/API do redirect, which is why the reusable workflow's own inneractions/checkoutstill works — but the outeruses:resolution does not.) So our five wrappers broke the moment the rename happened.Change — owner segment only
uses:now points toguard.ymlNetis/olympus/.github/workflows/guard.yml@v0.2.0issue-implement.ymlNetis/olympus/.github/workflows/implement.yml@v0.2.0issue-triage.ymlNetis/olympus/.github/workflows/triage.yml@v0.2.0pr-revise.ymlNetis/olympus/.github/workflows/revise.yml@v0.2.0pr-review.ymlNetis/olympus/.github/workflows/review.yml@v0.3.1Unchanged on purpose (these tags predate the Olympus rebrand and their frozen code expects the old names): the
@v0.2.0/@v0.3.1pins, theagent_ops_ref:inputs, and.agent-ops.json. Renaming those is a separate, larger upgrade (bump to a post-rename Olympus tag, e.g.v0.4.0, which reads.olympus.json+ takesolympus_ref).Verification
guard.ymlruns onpull_request, so this PR's own guard check uses the fixed wrapper — a green (resolving) run is the live proof the repoint works.Closes #164.
🤖 Generated with Claude Code