Skip to content

Move to new organization

Jump to bottom
Lukas Mittag edited this page Aug 9, 2023 · 5 revisions

There is a planned move to a new own organization eclipse/kuksa upcoming. This site will provide a guide for moving and splitting repositories. Therefore it discusses some techniques and problems. For every repository it could be a slightly different approach.

How to transfer a repository?

There are three possible ways to move repositories and code to the new organization. It would be possible to manually download a zip file and then put the stuff into the new designated repository. However forks and issues would need some manual handeling and the commit history would get lost. There is a designated transfer button in the Danger Zone of the repository settings. This will port the repository to a new owner. Forks would stay connected to the "old" repository. Issues can be downloaded and then uploaded again at the new location. The commit history would get preserved. If we want to split parts out of a repository (e.g. one repo for each provider) the preferred way would be to do a git filter-branch --subdirectory-filter <path_to_subdirectory> -- --all it would preserve the commit history and split out everything that is needed. Issues could be filter by tags (if they all have the right ones, downloaded and uploaded in the new location. For forks it is the same as with the transfer button option.

Summary

  • How to deal with git commit history: Use transfer button or git filter-branch --subdirectory-filter <path_to_subdirectory> -- --all
  • How to deal with issues: download the issues and upload it in the new location.
  • How to deal with forks: Either write some code to notify all fork owners or communciate it through public channels that the forks need to add a new remote origin.

See also: https://github.com/eclipse/kuksa.val/wiki/Proposal-for-splitting-of-KUKSA.val

Things to note

In the new eclipse-kuksa orga the actions do not have automatically write permissions. We need to check if they need them and add them in the actions. This would mean to add:

permissions: write

on top level of the action .yml files.

Clone this wiki locally