Preparing Git repository
Create new Git repository on gforge6
- Go to http://gforge6.eufus.eu/gf/project
- Press "Add New Project" button
- Fill project data - in the Temple project section select "Basic project with GIT support"
- Press "Submit" button
- Wait a moment (max. 10 minutes). Gforge will create a git repository for you
Image Removed
Create a repository git in an existing project (only for project administrators)
- Go to existing project on http://gforge6.eufus.eu/gf/project
- Open "Admin" tab
- Change "scm:" to "GIT"
- Press "Submit" button
- Wait a moment (max. 10 minutes). Gforge will create an empty git repository
Warning |
---|
SVN repository still exists! You can checkout data or commit changes. |
Image Removed
Migrating to Git
The section is based on: https://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git
...
Code Block |
---|
$ git svn clone https://<USERNAME>@gforge6gforge-next.eufus.eu/svn/<SVN_PROJECT_NAME>/ \
--authors-file=users.txt --no-metadata --prefix "" -s my_project
$ cd my_project |
Info |
---|
If the above command does not work, it is need to load the patch module for the git svn command: $ module load git-svn |
Info |
---|
title | Non-standard SVN layouts |
---|
|
If your SVN repository doesn’t have a standard layout, you need to provide the locations of your trunk, branches, and tags using the --trunk , --branches , and --tags command line options. For example, if you have branches stored in both the /branches directory and the /bugfixes directories, you would use the following command: Code Block |
---|
git svn clone --trunk=/trunk --branches=/branches --branches=/bugfixes --tags=/tags --authors-file=users.txt --no-metadata --prefix "" https://<USERNAME>@gforge6.eufus.eu/svn/<SVN_PROJECT_NAME> my_project |
![](/download/thumbnails/24087346/Zrzut%20ekranu%20%2837%29.png?version=1&modificationDate=1571218792528&api=v2)
|
...
Code Block |
---|
$ git remote add origin https://<USERNAME>@gforge6gitlab.eufus.eu/git/<GIT_PROJECT_NAME> |
...