ops forgejo release: add CRUD verbs #72

New issue

Closed

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

coilysiren commented

2026-05-25 00:25:41 +00:00

Owner

Problem

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

Scope

Add the following under coily ops forgejo release:

create --repo <owner/name> --tag <tag> [--name N] [--body-file PATH] [--draft] [--prerelease] -> POST /repos/{owner}/{repo}/releases
list --repo <owner/name> [--limit N] -> GET /repos/{owner}/{repo}/releases
view --repo <owner/name> --id ID -> GET /repos/{owner}/{repo}/releases/{id}
edit --repo <owner/name> --id ID [--name N] [--body-file PATH] [--draft=...] [--prerelease=...] -> PATCH /repos/{owner}/{repo}/releases/{id}
delete --repo <owner/name> --id ID -> DELETE /repos/{owner}/{repo}/releases/{id}

Out of scope (follow-up)

upload-asset -> POST /repos/{owner}/{repo}/releases/{id}/assets. Different mechanism (multipart/form-data with a file part) than the JSON CRUD verbs - worth a separate ticket so the asset-upload surface gets its own review.

Why

Third noun of the 5-noun sweep. Releases are the natural next surface after issues/labels for repo-level lifecycle automation.

**Problem** The `gh release` verb set has direct forgejo API equivalents but no coily surface. **Scope** Add the following under `coily ops forgejo release`: - `create --repo <owner/name> --tag <tag> [--name N] [--body-file PATH] [--draft] [--prerelease]` -> `POST /repos/{owner}/{repo}/releases` - `list --repo <owner/name> [--limit N]` -> `GET /repos/{owner}/{repo}/releases` - `view --repo <owner/name> --id ID` -> `GET /repos/{owner}/{repo}/releases/{id}` - `edit --repo <owner/name> --id ID [--name N] [--body-file PATH] [--draft=...] [--prerelease=...]` -> `PATCH /repos/{owner}/{repo}/releases/{id}` - `delete --repo <owner/name> --id ID` -> `DELETE /repos/{owner}/{repo}/releases/{id}` **Out of scope (follow-up)** `upload-asset` -> `POST /repos/{owner}/{repo}/releases/{id}/assets`. Different mechanism (multipart/form-data with a file part) than the JSON CRUD verbs - worth a separate ticket so the asset-upload surface gets its own review. **Why** Third noun of the 5-noun sweep. Releases are the natural next surface after issues/labels for repo-level lifecycle automation.

coilysiren referenced this issue

2026-05-25 00:42:19 +00:00

ops forgejo release: add upload-asset verb #75

coilysiren referenced this issue from a commit

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

feat(ops forgejo): add release CRUD verbs

coilysiren referenced this issue from a commit

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

feat(ops forgejo): add release CRUD verbs

coilysiren closed this issue

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