Detect Gitea ≥ the version that ships the new API.
Auto-create a matching project board, its columns, and drop each mirrored Issue/PR into the right column.
Ship the feature behind a beta flag, then make it the default after some real-world soak time.
I’ll keep this thread updated as soon as upstream merges the pieces we need. Thanks for hanging in there!
Hey @jayjay3108 — quick update after digging deeper.
The blocker is still the upstream **Projects API** work in Gitea, tracked in:
* go-gitea/gitea#14299 – core Projects/boards API
* go-gitea/gitea#31769 – follow-up for columns & cards (the bits that actually hold issues)
* go-gitea/gitea#30205 – first PR that starts wiring those endpoints together
**Why they matter**
| Item | What it gives us | Status |
|------|-----------------|--------|
| **#14299** | Create/list/update/delete *boards* | Open – targeted for ≥ v1.25 |
| **#31769** | API for *columns* & *cards* (so we can place issues/PRs in lanes) | Open |
| **#30205** | Draft implementation of the above | In review |
Once those land in a stable release, we can:
1. Detect Gitea ≥ the version that ships the new API.
2. Auto-create a matching project board, its columns, and drop each mirrored Issue/PR into the right column.
3. Ship the feature behind a beta flag, then make it the default after some real-world soak time.
I’ll keep this thread updated as soon as upstream merges the pieces we need. Thanks for hanging in there!
<!-- github-comment-id:2961367305 -->
Gitea's API has no endpoints for project boards and cards, so there is nothing on the other side to write to. Out of scope for this tool, marking as won't do.
Gitea's API has no endpoints for project boards and cards, so there is nothing on the other side to write to. Out of scope for this tool, marking as won't do.
<!-- github-comment-id:5506865775 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
add the Feature to mirror GitHub projects into gitea
@jayjay3108 happy to inform this is in the works an will be added in the next update.
Hey @jayjay3108 — quick update after digging deeper.
The blocker is still the upstream Projects API work in Gitea, tracked in:
Why they matter
Once those land in a stable release, we can:
I’ll keep this thread updated as soon as upstream merges the pieces we need. Thanks for hanging in there!
Gitea's API has no endpoints for project boards and cards, so there is nothing on the other side to write to. Out of scope for this tool, marking as won't do.