allod/tools
2
0
Fork 0
Code Issues 13 Pull requests Projects Releases Packages Wiki Activity Actions

Fork Forgejo to expose project APIs for forge project support #91

New issue
Open
opened 2026-07-07 21:41:20 +01:00 by vnprc-agent · 1 comment
vnprc-agent commented 2026-07-07 21:41:20 +01:00
Contributor
Copy link

User story: So that I can manage project boards through the same CLI workflow as issues, the server needs a supported project-board API before forge project can become a real command set.

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

Problem

forge cannot implement real project-board commands against forge.anarch.diy because the Forgejo API available here does not expose repository project endpoints. Probing repo, org, user, and current-user project paths returned 404.

Desired Outcome

Fork or patch Forgejo so project boards are exposed through a stable API, then implement forge project commands against that API.

Scope

Server/API work:

  • Identify the Forgejo project-board data model and existing web handlers.
  • Add authenticated API endpoints for listing, viewing, creating, editing, and deleting projects where Forgejo supports those operations in the UI.
  • Add issue/project assignment APIs if they are missing.
  • Preserve Forgejo permission checks; do not create an API bypass around UI authorization.

CLI work after API support exists:

  • Reintroduce forge project commands.
  • Copy gh project command names and flags where they map cleanly.
  • Document deviations where Forgejo's project model differs from GitHub's.

Boundary

Until this lands, organize issues with labels and milestones from the CLI and use the Forgejo web UI for project boards.

**User story:** So that I can manage project boards through the same CLI workflow as issues, the server needs a supported project-board API before `forge project` can become a real command set. _Part of the "Forge / workspace CLI tooling" arc._ --- ## Problem `forge` cannot implement real project-board commands against `forge.anarch.diy` because the Forgejo API available here does not expose repository project endpoints. Probing repo, org, user, and current-user project paths returned 404. ## Desired Outcome Fork or patch Forgejo so project boards are exposed through a stable API, then implement `forge project` commands against that API. ## Scope Server/API work: - Identify the Forgejo project-board data model and existing web handlers. - Add authenticated API endpoints for listing, viewing, creating, editing, and deleting projects where Forgejo supports those operations in the UI. - Add issue/project assignment APIs if they are missing. - Preserve Forgejo permission checks; do not create an API bypass around UI authorization. CLI work after API support exists: - Reintroduce `forge project` commands. - Copy `gh project` command names and flags where they map cleanly. - Document deviations where Forgejo's project model differs from GitHub's. ## Boundary Until this lands, organize issues with labels and milestones from the CLI and use the Forgejo web UI for project boards.
vnprc commented 2026-07-07 22:57:16 +01:00
Owner
Copy link

Here is a partially implemented PR to do exactly this on the official forgejo issue tracker. Ironically, Forgejo explicitly disallows AI-generated anything to be contributed to their project. The PR author gave up on the PR when he found out about the AI ban. This may be a good starting place to implement this feature.

https://codeberg.org/forgejo/forgejo/issues/5330

Here is a partially implemented PR to do exactly this on the official forgejo issue tracker. Ironically, Forgejo explicitly disallows AI-generated anything to be contributed to their project. The PR author gave up on the PR when he found out about the AI ban. This may be a good starting place to implement this feature. https://codeberg.org/forgejo/forgejo/issues/5330
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
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#91
No description provided.