2015-04-07 20:37:56 -04:00
|
|
|
# Project forking workflow
|
2015-03-03 15:31:54 -05:00
|
|
|
|
2016-01-27 05:26:04 -05:00
|
|
|
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 or can request it, we recommend working together in the same
|
|
|
|
repository since it is simpler. See our [GitLab Flow](gitlab_flow.md)
|
|
|
|
document more information about using branches to work together.
|
2015-03-03 15:31:54 -05:00
|
|
|
|
|
|
|
## Creating a fork
|
|
|
|
|
2016-01-27 06:00:51 -05:00
|
|
|
Forking a project is in most cases a two-step process.
|
2015-03-03 15:31:54 -05:00
|
|
|
|
2016-01-27 06:00:51 -05:00
|
|
|
1. Click on the fork button located in the middle of the page or a project's
|
|
|
|
home page right next to the stars button.
|
2015-03-03 15:31:54 -05:00
|
|
|
|
2016-01-27 06:00:51 -05:00
|
|
|
![Fork button](img/forking_workflow_fork_button.png)
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
1. 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.
|
|
|
|
|
|
|
|
![Choose namespace](img/forking_workflow_choose_namespace.png)
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
**Note:**
|
|
|
|
If the namespace you chose to fork the project to has another project with
|
|
|
|
the same path name, you will be presented with a warning that the forking
|
|
|
|
could not be completed. Try to resolve the error and repeat the forking
|
|
|
|
process.
|
|
|
|
|
|
|
|
![Path taken error](img/forking_workflow_path_taken_error.png)
|
|
|
|
|
|
|
|
---
|
2015-03-03 15:31:54 -05:00
|
|
|
|
2016-01-27 05:26:04 -05:00
|
|
|
After the forking is done, you can start working on the newly created
|
2016-07-12 11:03:29 -04:00
|
|
|
repository. There, you will have full [Owner](../user/permissions.md)
|
2016-01-27 06:00:51 -05:00
|
|
|
access, so you can set it up as you please.
|
2015-03-03 15:31:54 -05:00
|
|
|
|
|
|
|
## Merging upstream
|
|
|
|
|
2016-01-27 05:26:04 -05:00
|
|
|
Once you are ready to send your code back to the main project, you need
|
|
|
|
to create a merge request. Choose your forked project's main branch as
|
|
|
|
the source and the original project's main branch as the destination and
|
2016-01-27 06:00:51 -05:00
|
|
|
create the [merge request](merge_requests.md).
|
2015-03-03 15:31:54 -05:00
|
|
|
|
2015-03-03 15:38:45 -05:00
|
|
|
![Selecting branches](forking/branch_select.png)
|
2015-03-03 15:31:54 -05:00
|
|
|
|
2016-01-27 05:26:04 -05:00
|
|
|
You can then assign the merge request to someone to have them review
|
|
|
|
your changes. Upon pressing the 'Accept Merge Request' button, your
|
|
|
|
changes will be added to the repository and branch you're merging into.
|
2015-03-03 15:31:54 -05:00
|
|
|
|
2015-03-03 15:38:45 -05:00
|
|
|
![New merge request](forking/merge_request.png)
|
2015-03-03 15:31:54 -05:00
|
|
|
|
2016-01-27 05:26:04 -05:00
|
|
|
[gitlab flow]: https://about.gitlab.com/2014/09/29/gitlab-flow/ "GitLab Flow blog post"
|