Add forgejo repo create verb to coily ops forgejo repo #134
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 ops forgejo repoexposeslist / view / edit / fork / archive / deletebut nocreate. When an agent needs to create a new Forgejo repo (e.g. standing upcoilyco-flight-deck/websiteandcoilyco-bridge/website), there is no CorleyOps-audited path. The fallback is rawcurlagainst the Forgejo REST API with the/forgejo/api-tokenSecureString, which bypasses coily's argv validation + audit log.Ask
Add
coily ops forgejo repo createwrappingPOST /api/v1/orgs/{org}/repos(and ideallyPOST /api/v1/user/reposfor user-owned repos).Suggested shape, mirroring the existing repo verbs:
Notes:
privateunless--public/--private=falseis passed. Agent-chosen public visibility should be explicit, not the default ("public repos are indexed beyond recall")./forgejo/api-tokenresolution already used by the other HTTP repo verbs.Why now
Creating the two CorleyCo
websiterepos required dropping to curl because the CLI had no create verb. Routing repo creation through coily keeps the audit trail intact and removes the need to hand the API token to ad-hoc shell.