Skip to content
Snippets Groups Projects
Unverified Commit cff13ee0 authored by Ritesh Raj Sarraf's avatar Ritesh Raj Sarraf
Browse files

Document the Fork to Private Namespace workflow


For external developers, they may not have access right to push branches
into default repositories. We encourage users to fork the repository and
then prepare a merge request.

So updating the documentation accordingly.

Signed-off-by: default avatarRitesh Raj Sarraf <ritesh.sarraf@collabora.com>
parent 903f9728
No related branches found
No related tags found
1 merge request!101Document the Fork to Private Namespace workflow
Pipeline #160932 passed
......@@ -352,22 +352,19 @@ This guide assumes good working knowledge of git (see
specific guidelines) and an account with commit rights on GitLab (see
[Getting commit rights]( {{< ref "#getting-commit-rights" >}} ) for guidance).
## Fork the repository to private namespace
## Branch
Before commencing any work, the developer should fork the repository into their namespace
![](/images/gitlab-fork.png)
Propose changes by pushing a git branch to GitLab.
## Clone
Clone the forked repository
* Check out the git repository:
```
git clone https://gitlab.apertis.org/[group name]/[repository name].git
```
* Create a local branch and make code changes in there. The branch should have
the following naming convention: `wip/$username/$feature` or
`wip/$username/$taskid`. This branch should be pushed into the destination
repository: if developers lack permissions to do so they can ask to be
granted the needed privileges on the developer
[mailing list](https://lists.apertis.org/) or push to a personal repository
instead.
* Commit the changes (see the
[guidelines for making commits]( {{< ref "version_control.md#guidelines-for-making-commits" >}} )
), test them and check you are allowed to submit them under the project’s
......@@ -393,8 +390,6 @@ git commit -i -s
* Once the changes are ready to be reviewed, create a
[merge request on GitLab](https://docs.gitlab.com/ce/user/project/merge_requests/).
* The merge request should have the "Remove source branch when merge request
accepted" option enabled.
* If changes are not ready and some (strongly encouraged) early feedback is
required, the merge request should be
[marked as Work In Progress (WIP)](https://docs.gitlab.com/ce/user/project/merge_requests/work_in_progress_merge_requests.html).
......
static/images/gitlab-fork.png

57.7 KiB

0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment