Remove unavailable project commands from forge CLI #88

Open
opened 2026-07-07 21:41:19 +01:00 by vnprc-agent · 0 comments
Contributor

User story: So that I can trust the CLI help surface, forge should only advertise project commands once the server API can actually support them.

Part of the "Forge / workspace CLI tooling" arc.


Problem

forge help currently lists a top-level project resource, but forge project <command> only reports that project commands are unavailable because this Forgejo API does not expose repository project endpoints.

That is accurate as a diagnostic, but misleading as CLI surface: users see project in the resources list and expect at least read operations to work.

Desired Behavior

Remove the placeholder project resource from normal CLI help and dispatch until project API support exists. Keep the limitation documented in docs/forge.md if useful, but do not advertise forge project as a supported resource.

Follow-Up

If project support becomes important, track the server/API work separately and reintroduce forge project once the API exists.

**User story:** So that I can trust the CLI help surface, `forge` should only advertise project commands once the server API can actually support them. _Part of the "Forge / workspace CLI tooling" arc._ --- ## Problem `forge help` currently lists a top-level `project` resource, but `forge project <command>` only reports that project commands are unavailable because this Forgejo API does not expose repository project endpoints. That is accurate as a diagnostic, but misleading as CLI surface: users see `project` in the resources list and expect at least read operations to work. ## Desired Behavior Remove the placeholder `project` resource from normal CLI help and dispatch until project API support exists. Keep the limitation documented in `docs/forge.md` if useful, but do not advertise `forge project` as a supported resource. ## Follow-Up If project support becomes important, track the server/API work separately and reintroduce `forge project` once the API exists.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
allod/tools#88
No description provided.