github-starred/gitea-mirror
2
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-03-08 23:02:41 -05:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

Feature Request: mirroring Github Projects #4

New Issue
Open
opened 2025-10-31 15:26:56 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-10-31 15:26:56 -05:00
Owner
Copy Link

Originally created by @jayjay3108 on GitHub (May 22, 2025).

Originally assigned to: @arunavo4 on GitHub.

add the Feature to mirror GitHub projects into gitea

Originally created by @jayjay3108 on GitHub (May 22, 2025). Originally assigned to: @arunavo4 on GitHub. add the Feature to mirror GitHub projects into gitea
GiteaMirror added the enhancement label 2025-10-31 15:26:56 -05:00
GiteaMirror commented 2025-10-31 15:26:57 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Jun 4, 2025):

@jayjay3108 happy to inform this is in the works an will be added in the next update.

@arunavo4 commented on GitHub (Jun 4, 2025): @jayjay3108 happy to inform this is in the works an will be added in the next update.
GiteaMirror commented 2025-10-31 15:26:57 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Jun 11, 2025):

Hey @jayjay3108 — quick update after digging deeper.

The blocker is still the upstream Projects API work in Gitea, tracked in:

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!

@arunavo4 commented on GitHub (Jun 11, 2025): 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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea-mirror#4
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?