Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
arma_editing:gitlab_migration_5-3-17 [2017/05/03 15:48]
Theowningone
arma_editing:gitlab_migration_5-3-17 [2017/11/22 14:57] (current)
Line 7: Line 7:
   - To fix this path add ''/​members''​ after ''​clear-backblast''​ like so ''​git@code.clearbackblast.com:​clear-backblast/​members/​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. ​   - 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)