User Tools

Site Tools



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

Link to this comparison view

Both sides previous revision Previous revision
kb:bestpractices:scc:project-forking-workflow [2020/01/16 11:22]
joerg.hampel [In a nutshell]
kb:bestpractices:scc:project-forking-workflow [2020/01/16 11:33] (current)
Line 9: Line 9:
 //(taken from [[|Atlassian]])// //(taken from [[|Atlassian]])//
-==== In nutshell ====+ 
 +<WRAP left round tip 99%> 
 +“Fork” is not a Git operation — it just means you have made a copy of an existing repository and are doing new development on your copy. 
 +===== GitLab Documentation ===== 
 +Forking project is in most cases a two-step process. 
 +1. Click on the fork button located in between the star and clone buttons on the project’s home page. 
 +2. Once you do that, you’ll be presented with a screen where you can choose the namespace to fork to. Only namespaces (groups and your own namespace) where you have write access to, will be shown. Click on the namespace to create your fork there. 
 +//(taken from [[|]])// 
 +===== Reproducing a forked situation manually  =====
 //You are the ''user''. The guy who created the original repo is the ''maintainer''.// //You are the ''user''. The guy who created the original repo is the ''maintainer''.//
-    # create own private repo (this is remote 'origin')+    # clone own private repo (this is remote 'origin')
     git clone     git clone
Line 22: Line 41:
     git commit -a -m "this is my change"     git commit -a -m "this is my change"
-    # keep my private repo up to date+    # keep my private repo up to date with changes from public repo
     git pull upstream master     git pull upstream master
Line 35: Line 54:
-==== GitLab Documentation ==== +===== Other Resources =====
- +
-A detailed description can be found on [[|]].  +
- +
- +
-==== Other Resources ====+
   *   *
kb/bestpractices/scc/project-forking-workflow.txt · Last modified: 2020/01/16 11:33 by joerg.hampel