Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
a332e7bd
Commit
a332e7bd
authored
Apr 07, 2015
by
Patricio Cano
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Implemented changes suggested by Job.
parent
09dbe452
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
7 deletions
+8
-7
doc/workflow/forking_workflow.md
doc/workflow/forking_workflow.md
+8
-7
No files found.
doc/workflow/forking_workflow.md
View file @
a332e7bd
...
...
@@ -12,23 +12,24 @@ of the screen, close to the project's URL and right next to the stars button.
![
Fork button
](
forking/fork_button.png
)
Once you do that you will see a screen where you can choose the namespace, to where you want to add the fork. This page
will contain the groups you have write access to. Choose one of the groups and the project will be added there.
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.
![
Groups view
](
forking/groups.png
)
After the forking is done, you can start working on the newly created repository. There you will have full
Owner access,
so you can set it up as you please.
After the forking is done, you can start working on the newly created repository. There you will have full
[
Owner
](
../permissions/permissions.md
)
access,
so you can set it up as you please.
## Merging upstream
Once you are ready to send your code back to the main project, you need to create a
M
erge request. Choose your forked
Once you are ready to send your code back to the main project, you need to create a
m
erge request. Choose your forked
project's main branch as the source and the original project's main branch as the destination and create the merge request.
![
Selecting branches
](
forking/branch_select.png
)
You can then assign the
Merge Request to someone so they can review your changes. After they have reviewed them, the will
b
e added to the main project, if maintainer chooses to do s
o.
You can then assign the
merge request to someone to have them review your changes. Upon pressing the 'Accept Merge Request'
b
utton, your changes will be added to the repository and branch you're merging int
o.
![
New merge request
](
forking/merge_request.png
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment