rollout: port repo-recall + agent-guard + session-lattice to forgejo Actions #23
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?
Problem
Coily is the prototype for forgejo-canonical release. Once the bump-formula auth issue (#81) is resolved and coily's pipeline cuts an end-to-end release cleanly, the same pattern needs to roll out to the other 3 release-cutting
coilysiren/*repos:coilysiren/repo-recallcoilysiren/agent-guardcoilysiren/session-latticePer-repo migration
For each repo:
git ls-remote --tags forgejo | wc -lagainstgit tag | wc -l)..forgejo/workflows/release.ymlmirroringcoilysiren/coily/.forgejo/workflows/release.yml:runs-on: docker(notubuntu-latest)coilysiren/agentic-os/actions/{tag-bump,create-release,bump-formula}@mainformula_path:differs per repo (Formula/repo-recall.rb, etc.).github/workflows/release.yml.AGENTS.mdrelease-framework section to point at the forgejo flow (lift from coily's edit at f96dd14).Repo-specific notes
session-latticehas two Formulas (main + puller). The current github workflow bumps both in one job.bump-formulaaction only handles one path per call — call it twice in the forgejo job.repo-recallhas no scoop / Windows path, simplest port.agent-guardhas the smallest workflow, also straightforward.Don't start until: #81 is resolved (auto-token bump-formula auth) and coily has cut a clean end-to-end release. No point copy-pasting the same auth limitation across 3 more repos.