ops forgejo label: add CRUD verbs #71

New issue

Closed

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

coilysiren commented

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

Owner

Problem

The gh label verb set (create, list, edit, delete) has direct forgejo API equivalents but no coily surface. Agents that want to enforce a per-repo label taxonomy still have to drop to curl + SSM.

Scope

Add the following under coily ops forgejo label:

create --repo <owner/name> --name N --color HEX [--description-file PATH] -> POST /repos/{owner}/{repo}/labels
list --repo <owner/name> -> GET /repos/{owner}/{repo}/labels
edit --repo <owner/name> --id ID [--name N] [--color HEX] [--description-file PATH] -> PATCH /repos/{owner}/{repo}/labels/{id}
delete --repo <owner/name> --id ID -> DELETE /repos/{owner}/{repo}/labels/{id}

edit and delete take --id (forgejo's native key for labels) rather than --name. coily ops forgejo label list prints the id, name, and color so the operator can resolve a name -> id without a second tool. A name-based shorthand can come later if it earns its weight.

Color is validated as a 6-hex-digit string (with or without leading #). Description is taken from a file to keep multi-word values past the lockdown metacharacter gate.

Why

Second noun of the 5-noun sweep, after issue (coilysiren/coily#69, coilysiren/coily#70). Lowest-frequency surface, smallest verb count - good shake-out for the per-noun cadence.

**Problem** The `gh label` verb set (`create`, `list`, `edit`, `delete`) has direct forgejo API equivalents but no coily surface. Agents that want to enforce a per-repo label taxonomy still have to drop to curl + SSM. **Scope** Add the following under `coily ops forgejo label`: - `create --repo <owner/name> --name N --color HEX [--description-file PATH]` -> `POST /repos/{owner}/{repo}/labels` - `list --repo <owner/name>` -> `GET /repos/{owner}/{repo}/labels` - `edit --repo <owner/name> --id ID [--name N] [--color HEX] [--description-file PATH]` -> `PATCH /repos/{owner}/{repo}/labels/{id}` - `delete --repo <owner/name> --id ID` -> `DELETE /repos/{owner}/{repo}/labels/{id}` `edit` and `delete` take `--id` (forgejo's native key for labels) rather than `--name`. `coily ops forgejo label list` prints the id, name, and color so the operator can resolve a name -> id without a second tool. A name-based shorthand can come later if it earns its weight. Color is validated as a 6-hex-digit string (with or without leading `#`). Description is taken from a file to keep multi-word values past the lockdown metacharacter gate. **Why** Second noun of the 5-noun sweep, after `issue` (coilysiren/coily#69, coilysiren/coily#70). Lowest-frequency surface, smallest verb count - good shake-out for the per-noun cadence.

coilysiren referenced this issue from a commit

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

feat(ops forgejo): add label CRUD verbs

coilysiren closed this issue

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

coilysiren referenced this issue from a commit

2026-05-26 03:57:22 +00:00

feat(ops forgejo): add label CRUD verbs