From e35cb5a025e3f47fd7ab237b5cf368aa3b9b319d Mon Sep 17 00:00:00 2001 From: Zeger-Jan van de Weg Date: Mon, 28 Mar 2016 21:40:49 +0200 Subject: Docs for the new branch button [ci-skip] --- doc/gitlab-basics/basicsimages/new_branch_button.png | Bin 0 -> 120622 bytes doc/gitlab-basics/create-branch.md | 9 +++++++++ 2 files changed, 9 insertions(+) create mode 100644 doc/gitlab-basics/basicsimages/new_branch_button.png diff --git a/doc/gitlab-basics/basicsimages/new_branch_button.png b/doc/gitlab-basics/basicsimages/new_branch_button.png new file mode 100644 index 00000000000..394c139e17e Binary files /dev/null and b/doc/gitlab-basics/basicsimages/new_branch_button.png differ diff --git a/doc/gitlab-basics/create-branch.md b/doc/gitlab-basics/create-branch.md index 7556b0f663e..9d688b9389b 100644 --- a/doc/gitlab-basics/create-branch.md +++ b/doc/gitlab-basics/create-branch.md @@ -32,6 +32,15 @@ Fill out the information required: ![Branch info](basicsimages/branch_info.png) +## From an issue +When an issue should be resolved one could also create a branch on the issue page. A button is displayed after the description unless there is already a branch or a referenced merge request. + +![New Branch Button](basicsimages/new_branch_button.png) + +The branch created diverges from the default branch of the project, usually `master`. The branch name will be based on the title of the issue and as suffix its ID. Thus the example screenshot above will yield a branch named `et-cum-et-sed-expedita-repellat-consequatur-ut-assumenda-numquam-rerum-2`. +After the branch is created the user can edit files in the repository to fix the issue. When a merge request is created the +description field will display `Closes #2` to use the issue closing pattern. This will close the issue once the merge request is merged. + ### Note: You will be able to find and select the name of your branch in the white box next to a project's name: -- cgit v1.2.1