See https://github.com/go-gitea/gitea/pull/26051
---------
Signed-off-by: jolheiser <john.olheiser@gmail.com>
Co-authored-by: JonRB <4564448+eeyrjmr@users.noreply.github.com>
(cherry picked from commit 4033d95dbf
)
1.8 KiB
date | title | slug | sidebar_position | toc | draft | aliases | menu | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2019-04-15T17:29:00+08:00 | Migrations Interfaces | migrations-interfaces | 55 | false | false |
|
|
Migration Features
Complete migrations were introduced in Gitea 1.9.0. It defines two interfaces to support migrating repository data from other Git host platforms to Gitea or, in the future, migrating Gitea data to other Git host platforms.
Currently, migrations from GitHub, GitLab, and other Gitea instances are implemented.
First of all, Gitea defines some standard objects in packages modules/migration.
They are Repository
, Milestone
, Release
, ReleaseAsset
, Label
, Issue
, Comment
, PullRequest
, Reaction
, Review
, ReviewComment
.
Downloader Interfaces
To migrate from a new Git host platform, there are two steps to be updated.
- You should implement a
Downloader
which will be used to get repository information. - You should implement a
DownloaderFactory
which will be used to detect if the URL matches and create the aboveDownloader
.- You'll need to register the
DownloaderFactory
viaRegisterDownloaderFactory
oninit()
.
- You'll need to register the
You can find these interfaces in downloader.go.
Uploader Interface
Currently, only a GiteaLocalUploader
is implemented, so we only save downloaded
data via this Uploader
to the local Gitea instance. Other uploaders are not supported at this time.
You can find these interfaces in uploader.go.