... | ... | @@ -2,6 +2,12 @@ |
|
|
|
|
|
# FAQ Migration from INRIA Forge to INRIA Gitlab
|
|
|
|
|
|
## Planning the migration
|
|
|
|
|
|
INRIA Forge project administrators and/or users need to coordinate to decide *when* and *how* to perform these migrations. It's also important to decide *what* exactly needs to be migrated, since you may not need to keep everything.
|
|
|
|
|
|
Coordination is paramount because if, as a project admin, you migrate for example the source control repository without telling the users, some of them might still use the old repository on the forge for checkouts or commits.
|
|
|
|
|
|
## Migration of source control repositories
|
|
|
|
|
|
INRIA gitlab is restricted to git (no subversion anymore), so for subversion users unfamiliar with git, you should take the time to read and understand the basic differences between subversion and git. If you want to stay with subversion, there is no alternative at INRIA, but you can go to SourceSup https://sourcesup.renater.fr/, which is actively maintained by Renater.
|
... | ... | |