ops forgejo repo: add repo-level CRUD verbs #73

New issue

Closed

opened 2026-05-25 00:28:02 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-05-25 00:28:02 +00:00

Owner

Problem

The gh repo verb set has direct forgejo API equivalents but no coily surface.

Scope

Add the following under coily ops forgejo repo:

list [--query Q] [--limit N] -> GET /repos/search (text-match on name; an owner-name shortcut can land later if it earns its weight)
view --repo <owner/name> -> GET /repos/{owner}/{repo}
edit --repo <owner/name> [--description-file PATH] [--private=...] [--has-issues=...] [--has-wiki=...] -> PATCH /repos/{owner}/{repo}
fork --repo <owner/name> [--organization NAME] -> POST /repos/{owner}/{repo}/forks
archive --repo <owner/name> -> PATCH /repos/{owner}/{repo} with {archived: true} (shortcut for the gh-equivalent flow)
delete --repo <owner/name> -> DELETE /repos/{owner}/{repo} (admin-gated server-side)

Booleans on edit use cli/v3 IsSet semantics so "leave alone" and "set to false" stay distinguishable. --description-file rather than inline --description for the lockdown gate.

Why

Fourth noun of the 5-noun sweep. Repo-level CRUD is the natural completion of the issue/label/release surface for cross-repo lifecycle automation.

**Problem** The `gh repo` verb set has direct forgejo API equivalents but no coily surface. **Scope** Add the following under `coily ops forgejo repo`: - `list [--query Q] [--limit N]` -> `GET /repos/search` (text-match on name; an owner-name shortcut can land later if it earns its weight) - `view --repo <owner/name>` -> `GET /repos/{owner}/{repo}` - `edit --repo <owner/name> [--description-file PATH] [--private=...] [--has-issues=...] [--has-wiki=...]` -> `PATCH /repos/{owner}/{repo}` - `fork --repo <owner/name> [--organization NAME]` -> `POST /repos/{owner}/{repo}/forks` - `archive --repo <owner/name>` -> `PATCH /repos/{owner}/{repo}` with `{archived: true}` (shortcut for the gh-equivalent flow) - `delete --repo <owner/name>` -> `DELETE /repos/{owner}/{repo}` (admin-gated server-side) Booleans on `edit` use cli/v3 `IsSet` semantics so "leave alone" and "set to false" stay distinguishable. `--description-file` rather than inline `--description` for the lockdown gate. **Why** Fourth noun of the 5-noun sweep. Repo-level CRUD is the natural completion of the issue/label/release surface for cross-repo lifecycle automation.

coilysiren referenced this issue from a commit

2026-05-25 01:23:11 +00:00

feat(ops forgejo): add repo CRUD verbs

coilysiren referenced this issue from a commit

2026-05-25 06:35:10 +00:00

feat(ops forgejo): add repo CRUD verbs

coilysiren closed this issue

2026-05-25 06:35:10 +00:00