github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-22 05:15:42 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Migrate gitea from/to other git providers with projects API support #14710

New Issue
Open
opened 2025-11-02 11:20:49 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 11:20:49 -06:00
Owner
Copy Link

Originally created by @printfdebugging on GitHub (Jul 6, 2025).

Feature Description

i created a private repository with a project, and that project organized all the issues quite nicely. let's say gitea.com announces end of life sometime in future, then i have to manually recreate the project(s) as the migration tool doesn't include the projects in the repository.

it would be really nice if we also migrate the projects.

Screenshots

No response

Originally created by @printfdebugging on GitHub (Jul 6, 2025). ### Feature Description i created a private repository with a project, and that project organized all the issues quite nicely. let's say gitea.com announces end of life sometime in future, then i have to manually recreate the project(s) as the migration tool doesn't include the projects in the repository. it would be really nice if we also migrate the projects. ### Screenshots _No response_
GiteaMirror added the type/proposaltype/feature labels 2025-11-02 11:20:49 -06:00
GiteaMirror commented 2025-11-02 11:20:50 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jul 6, 2025):

Gitea has full featured API and I think it is the "receiver" side's task to read any data they are interested in.

let's say gitea.com announces end of life sometime in future, ...

IIRC the goal of "gitea.com" isn't to be a large & general purpose public git service, it is still recommended to use GitHub or a self-hosted Gitea instance.

@wxiaoguang commented on GitHub (Jul 6, 2025): Gitea has full featured API and I think it is the "receiver" side's task to read any data they are interested in. > let's say gitea.com announces end of life sometime in future, ... IIRC the goal of "gitea.com" isn't to be a large & general purpose public git service, it is still recommended to use GitHub or a self-hosted Gitea instance.
GiteaMirror commented 2025-11-02 11:20:50 -06:00
Author
Owner
Copy Link

@printfdebugging commented on GitHub (Jul 6, 2025):

thanks for the quick reply :)

@printfdebugging commented on GitHub (Jul 6, 2025): thanks for the quick reply :)
GiteaMirror commented 2025-11-02 11:20:50 -06:00
Author
Owner
Copy Link

@printfdebugging commented on GitHub (Jul 6, 2025):

@wxiaoguang i have gitea running locally as a service and when i migrated from gitea.com to the local gitea instance, still the project wasn't cloned. as you taked about the "receiver side", doesn't gitea copy the projects when on receiver side?

@printfdebugging commented on GitHub (Jul 6, 2025): @wxiaoguang i have gitea running locally as a service and when i migrated from gitea.com to the local gitea instance, still the project wasn't cloned. as you taked about the "receiver side", doesn't gitea copy the projects when on receiver side?
GiteaMirror commented 2025-11-02 11:20:50 -06:00
Author
Owner
Copy Link

@printfdebugging commented on GitHub (Jul 6, 2025):

looking at the api, i don't see any projects flag, you said the api is fully featured, am i missing anything?

@printfdebugging commented on GitHub (Jul 6, 2025): looking at the [api](https://gitea.com/api/swagger#/repository/repoMigrate), i don't see any projects flag, you said the api is fully featured, am i missing anything?
GiteaMirror commented 2025-11-02 11:20:51 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jul 6, 2025):

Hmm, just found that the "Projects API" is on the way ([FEATURE] API for projects #14299, feat: api endpoints for projects #28111 ), if there would be progresses, maybe we can have them in 1.25

So this feature request depends on the projects API

@wxiaoguang commented on GitHub (Jul 6, 2025): Hmm, just found that the "Projects API" is on the way ([FEATURE] API for projects #14299, feat: api endpoints for projects #28111 ), if there would be progresses, maybe we can have them in 1.25 ---- So this feature request depends on the projects API
GiteaMirror commented 2025-11-02 11:20:51 -06:00
Author
Owner
Copy Link

@buzzy commented on GitHub (Jul 31, 2025):

Gitea has full featured API and I think it is the "receiver" side's task to read any data they are interested in.

let's say gitea.com announces end of life sometime in future, ...

IIRC the goal of "gitea.com" isn't to be a large & general purpose public git service, it is still recommended to use GitHub or a self-hosted Gitea instance.

"full featured"? Ok, then please let me know how I can list user-projects through the API. I am unable to find it in the swagger definition. Also, how do I add a user-project through the API? Thanks!

@buzzy commented on GitHub (Jul 31, 2025): > Gitea has full featured API and I think it is the "receiver" side's task to read any data they are interested in. > > > let's say gitea.com announces end of life sometime in future, ... > > IIRC the goal of "gitea.com" isn't to be a large & general purpose public git service, it is still recommended to use GitHub or a self-hosted Gitea instance. "full featured"? Ok, then please let me know how I can list user-projects through the API. I am unable to find it in the swagger definition. Also, how do I add a user-project through the API? Thanks!
GiteaMirror commented 2025-11-02 11:20:51 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jul 31, 2025):

Gitea has full featured API and I think it is the "receiver" side's task to read any data they are interested in.

let's say gitea.com announces end of life sometime in future, ...

IIRC the goal of "gitea.com" isn't to be a large & general purpose public git service, it is still recommended to use GitHub or a self-hosted Gitea instance.

"full featured"? Ok, then please let me know how I can list user-projects through the API. I am unable to find it in the swagger definition. Also, how do I add a user-project through the API? Thanks!

See the comment above: https://github.com/go-gitea/gitea/issues/34969#issuecomment-3041211325

And the code is always there, so you can also write new code or change existing code to satisfy your requirements.

@wxiaoguang commented on GitHub (Jul 31, 2025): > > Gitea has full featured API and I think it is the "receiver" side's task to read any data they are interested in. > > > let's say gitea.com announces end of life sometime in future, ... > > > > > > IIRC the goal of "gitea.com" isn't to be a large & general purpose public git service, it is still recommended to use GitHub or a self-hosted Gitea instance. > > "full featured"? Ok, then please let me know how I can list user-projects through the API. I am unable to find it in the swagger definition. Also, how do I add a user-project through the API? Thanks! See the comment above: https://github.com/go-gitea/gitea/issues/34969#issuecomment-3041211325 And the code is always there, so you can also write new code or change existing code to satisfy your requirements.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/feature type/proposal
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#14710
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?