third_party
/
gitea
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
11682 Commits
2 Branches
0 Tags
242 MiB
 
 
 
 
 
 
Tag: Branch: Tree: e3c626834b
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e3c626834b'
${ noResults }
gitea/docs/content/doc/developers/migrations.en-us.md

1.8 KiB
Raw Blame History

date title slug weight toc draft menu
2019-04-15T17:29:00+08:00 Migrations Interfaces migrations-interfaces 30 false false [{sidebar [{parent developers} {name Migrations Interfaces} {weight 55} {identifier migrations-interfaces}]}]

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/migrations/base.
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 above Downloader.
    • You'll need to register the DownloaderFactory via RegisterDownloaderFactory on init().

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.