Remove superseded deploy/repo-recall.yml after repo-recall#97 migration #174
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Remove the superseded
deploy/repo-recall.ymlcoilysiren/repo-recall#97 migrated repo-recall's deploy off GitHub Actions to
the in-cluster Forgejo runner + registry, and moved the canonical deploy
manifest into the repo-recall repo at
deploy/repo-recall.yml(matching thepattern backend established in coilysiren/backend#25, which removed its
infrastructure copy).
infrastructure/deploy/repo-recall.ymlis now a stale duplicate. It stillreferences the GHCR api image and lacks the deployer ServiceAccount.
Work
infrastructure/deploy/repo-recall.yml.infrastructure/docs/repo-recall-deploy.md(or rewrite it to point atthe in-repo manifest + Forgejo pipeline). It currently documents the dead
GHCR + pull-side systemd path.
Source of truth is now
coilysiren/repo-recall:deploy/repo-recall.yml.