diff options
| author | Patricio Cano <patricio@gitlab.com> | 2015-03-03 21:44:53 -0800 |
|---|---|---|
| committer | Patricio Cano <patricio@gitlab.com> | 2015-03-03 21:44:53 -0800 |
| commit | 09dbe452e3a57ab6ec68b0af76b32502cbeec00e (patch) | |
| tree | bc6e1510b19df8e138407fd2302b04ed0957649f /doc/workflow | |
| parent | 92b1b15f6f2579159160bde3efc41d632a92453e (diff) | |
| download | gitlab-ce-09dbe452e3a57ab6ec68b0af76b32502cbeec00e.tar.gz | |
Corrected sentence about GitLab Flow
Diffstat (limited to 'doc/workflow')
| -rw-r--r-- | doc/workflow/forking_workflow.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/workflow/forking_workflow.md b/doc/workflow/forking_workflow.md index dee9e432140..2c680a4c124 100644 --- a/doc/workflow/forking_workflow.md +++ b/doc/workflow/forking_workflow.md @@ -1,7 +1,9 @@ # Code forking workflow Forking a project to your own namespace is useful if you have no write access to the project you want to contribute -to. If you do have write access, we recommend using the **[Code Branching Workflow](https://about.gitlab.com/2014/09/29/gitlab-flow/)**. +to. If you do have write access or can request it we recommend working together in the same repository since it is simpler. +See our **[GitLab Flow](https://about.gitlab.com/2014/09/29/gitlab-flow/)** article for more information about using +branches to work together. ## Creating a fork |