Differences

This shows you the differences between two versions of the page.

Link to this comparison view

arma_editing:gitlab_migration_5-3-17 [2017/05/03 16:02]
Theowningone
arma_editing:gitlab_migration_5-3-17 [2017/11/22 14:57]
Line 1: Line 1:
-~~Title:​Gitlab Migration — 5/3/2017~~ 
  
-==== SmartGit === 
- 
-  - Open SmartGit and find the repository with the broken remote, double click on it to select it. 
-  - In the top menu select **Remote -> Properties**,​ it should show you a url like such ''​git@code.clearbackblast.com:​clear-backblast/​cbb-mods-a3.git''​. ​ 
-  - To fix this path add ''/​members''​ after ''​clear-backblast''​ like so ''​git@code.clearbackblast.com:​clear-backblast/​members/​cbb-mods-a3.git''​. 
-  - Press **Store** to save it changes and continue as usual. ​ 
- 
-==== Git CLI === 
- 
-  - Open your choice of shell session, and navigate to the root folder of the Repository with the broken remote. 
-  - Run ''​git remote -v''​ to list your current remotes, there should be a group that looks something like: <​code>​ 
-origin ​ git@code.clearbackblast.com:​clear-backblast/​members/​cbb-mods-a3.git (fetch) 
-origin ​ git@code.clearbackblast.com:​clear-backblast/​members/​cbb-mods-a3.git (push) 
-</​code>​ 
-  - To fix this path add ''/​members''​ after ''​clear-backblast''​ like so ''​git@code.clearbackblast.com:​clear-backblast/​members/​cbb-mods-a3.git''​. 
-  - Run ''​git remote set-url <​name>​ <​new-path>''​ to change it to the correct path. Name is likely ''​origin''​ like above, but reference your own remotes list to be sure. 
-  - Run ''​git remote -v''​ again to confirm the change did what you wanted. 
-  - Continue using git as usual. 
  • Last modified: 7 years ago
  • (external edit)