mirror of
https://github.com/go-gitea/gitea.git
synced 2026-10-26 06:16:56 +09:00
Lunny Xiaoandbircni
a2da5cd7b5
Add migration from Bitbucket Server (Data Center). It has no issues, wiki, milestones or releases, so those are not offered. Migrated: git data with tags and LFS, and pull requests with state, draft flag, merge commit/base, comments, approvals and inline code comments including resolved threads. Multi-line ranges become a `Lines a-b:` text prefix, as Gitea anchors code comments to one line. Auth is an HTTP access token (personal, project or repository) or username/password; 429 responses are retried. Changes outside the downloader: - `ReviewComment.Resolved`, applied by the uploader. - The uploader creates a fork PR's head branch from its head commit when already in the repository, instead of fetching the fork (Bitbucket keeps it in `refs/pull-requests/<id>/from`; private forks need credentials). Tested with unit tests, responses recorded from Bitbucket 10.5.1, and an end-to-end migration. Independent of https://github.com/go-gitea/gitea/pull/38607 (Bitbucket Cloud); the service type enum value needs adjusting for whichever lands second. --------- Co-authored-by: bircni <bircni@icloud.com>
70 lines
2.3 KiB
Go
70 lines
2.3 KiB
Go
// Copyright 2019 The Gitea Authors. All rights reserved.
|
|
// SPDX-License-Identifier: MIT
|
|
|
|
package migration
|
|
|
|
import "time"
|
|
|
|
// Reviewable can be reviewed
|
|
type Reviewable interface {
|
|
GetLocalIndex() int64
|
|
GetContext() DownloaderContext
|
|
|
|
// GetForeignIndex presents the foreign index, which could be misused:
|
|
// For example, if there are 2 Gitea sites: site-A exports a dataset, then site-B imports it:
|
|
// * if site-A exports files by using its LocalIndex
|
|
// * from site-A's view, LocalIndex is site-A's IssueIndex while ForeignIndex is site-B's IssueIndex
|
|
// * but from site-B's view, LocalIndex is site-B's IssueIndex while ForeignIndex is site-A's IssueIndex
|
|
//
|
|
// So the exporting/importing must be paired, but the meaning of them looks confusing then:
|
|
// * either site-A and site-B both use LocalIndex during dumping/restoring
|
|
// * or site-A and site-B both use ForeignIndex
|
|
GetForeignIndex() int64
|
|
}
|
|
|
|
// enumerate all review states
|
|
const (
|
|
ReviewStatePending = "PENDING"
|
|
ReviewStateApproved = "APPROVED"
|
|
ReviewStateChangesRequested = "CHANGES_REQUESTED"
|
|
ReviewStateCommented = "COMMENTED"
|
|
ReviewStateRequestReview = "REQUEST_REVIEW"
|
|
)
|
|
|
|
// Review is a standard review information
|
|
type Review struct {
|
|
ID int64
|
|
IssueIndex int64 `yaml:"issue_index"`
|
|
ReviewerID int64 `yaml:"reviewer_id"`
|
|
ReviewerName string `yaml:"reviewer_name"`
|
|
Official bool
|
|
CommitID string `yaml:"commit_id"`
|
|
Content string
|
|
CreatedAt time.Time `yaml:"created_at"`
|
|
State string // PENDING, APPROVED, REQUEST_CHANGES, or COMMENT
|
|
Comments []*ReviewComment
|
|
}
|
|
|
|
// GetExternalName ExternalUserMigrated interface
|
|
func (r *Review) GetExternalName() string { return r.ReviewerName }
|
|
|
|
// GetExternalID ExternalUserMigrated interface
|
|
func (r *Review) GetExternalID() int64 { return r.ReviewerID }
|
|
|
|
// ReviewComment represents a review comment
|
|
type ReviewComment struct {
|
|
ID int64
|
|
InReplyTo int64 `yaml:"in_reply_to"`
|
|
Content string
|
|
TreePath string `yaml:"tree_path"`
|
|
DiffHunk string `yaml:"diff_hunk"`
|
|
Position int
|
|
Line int
|
|
CommitID string `yaml:"commit_id"`
|
|
PosterID int64 `yaml:"poster_id"`
|
|
Resolved bool // the conversation of this (first) comment is resolved
|
|
Reactions []*Reaction
|
|
CreatedAt time.Time `yaml:"created_at"`
|
|
UpdatedAt time.Time `yaml:"updated_at"`
|
|
}
|