tahoe-lafs/web-landing-page
4
1
Fork 1
Code Issues 6 Pull requests 3 Actions Activity

Describe how to migrate this repository elsewhere #32

New issue
Open
opened 2025-08-14 12:48:14 +00:00 by btlogy · 2 comments
btlogy commented 2025-08-14 12:48:14 +00:00
Owner
Copy link

This repository has been developed first on Gitea, than easily migrated to Forgejo (which is compatible).

Migrating it to GH is another story as I have not found a way to cover the PRs and issues.

This issue will try to highlight some option for anyone who wants to propose a migration plan.

This repository has been developed first on Gitea, than easily migrated to Forgejo (which is compatible). Migrating it to GH is another story as I have not found a way to cover the PRs and issues. This issue will try to highlight some option for anyone who wants to propose a migration plan.
btlogy commented 2025-08-14 13:09:05 +00:00
Author
Owner
Copy link

The easiest way to migrate to GH would be to:

  1. archive this repository on Forgejo (which should prevent further push to the current mirror on GH),
  2. enable any features on this mirror (e.g. issues and actions) to make it work as expected,
  3. change the workflows to use GHA (basically renaming .forgejo path to .github).

But, this will break all the #XX links to issue/PRs in the commit messages, unless: someone re-create/migrate all those from Forgejo too (I've not identified an existing tool for this)

Another way would be to overwrite the current mirror from scratch to get rid of those #XX links, but this would also mean dropping the whole history (which I think could be helpful for future changes).

The easiest way to migrate to GH would be to: 1. archive this repository on Forgejo (which should prevent further push to the current [mirror](https://github.com/tahoe-lafs/web-landing-page/) on GH), 2. enable any features on this [mirror](https://github.com/tahoe-lafs/web-landing-page/) (e.g. issues and actions) to make it work as expected, 3. change the workflows to use GHA (basically renaming `.forgejo` path to `.github`). But, this will break all the #XX links to issue/PRs in the commit messages, unless: someone re-create/migrate all those from Forgejo too (I've not identified an existing tool for this) Another way would be to overwrite the current mirror from scratch to get rid of those #XX links, but this would also mean dropping the whole history (which I think could be helpful for future changes).
btlogy changed title from Describe how to migrate this repository to GH to Describe how to migrate this repository elsewhere 2025-08-19 08:23:34 +00:00
btlogy commented 2025-08-19 08:26:51 +00:00
Author
Owner
Copy link

An other target to be considered is CodeBerg, which provide migration tool covering issues and pull-request.

Recently, CodeBerg also support actions (experimental), which could cover the CI/CD requirements of this repository.

An other target to be considered is CodeBerg, which provide migration tool covering issues and pull-request. Recently, CodeBerg also support actions (experimental), which could cover the CI/CD requirements of this repository.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
rework-about
30.fix-cleanup
30.rework-for-prod
12.rework-contribute
12.rework-about
16.fix-mobile-width
add-readme
no-font-override
12.cut-teaser-background
12.better-images
16.equal-height-boxes
12.disable-share-links
12.deps-update
remove-patern
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/web-landing-page#32
No description provided.
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?