Expand repo migration guide #142

Merged
n merged 2 commits from migrating-repos into master 11 months ago
n commented 11 months ago
Collaborator

This PR expands the Repo Migration guide and moves the Access Token Generation part into a different guide.

I also removed the install Gitea part because it seemed outside Codeberg Docs' scope, and if people were looking to migrate away, they would probably have an alternative Gitea instance ready.

This PR expands the Repo Migration guide and moves the Access Token Generation part into a different guide. I also removed the install Gitea part because it seemed outside Codeberg Docs' scope, and if people were looking to migrate away, they would probably have an alternative Gitea instance ready.
n added the
Kind: Documentation
Kind: Enhancement
labels 11 months ago
n added 1 commit 11 months ago
fnetX approved these changes 11 months ago
fnetX left a comment
Collaborator

Nice, thanks.

Nice, thanks.
On your primary Gitea instance at [Codeberg](https://codeberg.org) you need to go to `Profiles and Settings...` (on the top right corner), then to [`Settings`](https://codeberg.org/user/settings) (the option with the wrench symbol) and then to the [`Applications`-option](https://codeberg.org/user/settings/applications) (in the middle of the top bar).
Click on the `Generate Token`-button to generate a new application token.
### Migrating from Gitea
To migrate from a Gitea instance, you will first need to [create an access token](/advanced/access-token/) on the Gitea instance with your repository. Don't forget to delete the access token when you are finished.
Collaborator

... maybe point out that you can also migrate without an access token, but this will only do a Git migration?

I think this is not obvious to everyone?

Maybe reword to

To migrate not only the Git content but your metadata from a Gitea instance, you will first need to create an access token on the Gitea instance with your repository. Don't forget to delete the access token when you are finished.

or something like that?

... maybe point out that you can also migrate without an access token, but this will only do a Git migration? I think this is not obvious to everyone? Maybe reword to > To migrate not only the Git content but your metadata from a Gitea instance, you will first need to [create an access token](/advanced/access-token/) on the Gitea instance with your repository. Don't forget to delete the access token when you are finished. or something like that?
n marked this conversation as resolved
Just remember to revoke the access token as soon as you are finished.
Once you've filled out all the fields, click the `Migrate Repository` button.
Migration might take a while, depending on how large the repo is.
Collaborator

It will timeout after a while (20 minutes at the moment AFAICT), maybe mention this and if something goes wrong people should ask in the Community Issue Tracker? Like, having a little troubleshooting, since migration issues have been one of the most frequent problems on Codeberg IMO.

It will timeout after a while (20 minutes at the moment AFAICT), maybe mention this and if something goes wrong people should ask in the Community Issue Tracker? Like, having a little troubleshooting, since migration issues have been one of the most frequent problems on Codeberg IMO.
n marked this conversation as resolved
n added 1 commit 11 months ago
n commented 11 months ago
Poster
Collaborator

@fnetX Thanks for the review. I've implemented your suggestions.

@fnetX Thanks for the review. I've implemented your suggestions.
n referenced this issue from a commit 11 months ago
n merged commit d33e360dbc into master 11 months ago
n deleted branch migrating-repos 11 months ago

Reviewers

fnetX approved these changes 11 months ago
The pull request has been merged as d33e360dbc.
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This pull request currently doesn't have any dependencies.

Loading…
There is no content yet.