Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

can I create a feature branch from a open issue in Gitlab?

I can't find a 'create branch' button in the page; guessing I am missing something obvious?

enter image description here

from gitlab members section, I myself is displayed as 'maintainer' of the project; I initially imported this project from a github repo using github url. Is this expected?

==== 2020.07.05 ======

answering myself: in my case, the issues was created from a defect reported by github application security analysis CI run, and it is automatically marked as 'confidential', and for confidential issue, by default, there is no action available to create merge request and feature request.

in order to enable MR, I had to edit the 'confidentiality' label to toggle it off.

enter image description here

I am using gitlab.com and version below:

enter image description here

like image 250
sqr Avatar asked Jul 02 '20 10:07

sqr


People also ask

How do you create a new branch for an issue in GitLab?

go in the issue, find the "Create branch" button and click on the little arrow to expand the details. In the "Source (branch or tag)" Field, your default branch (Master in our example) will be pre-selected. Change that entry to UAT (you'll have to type it in since there's no dropdown menu). click on Create branch.

How do I push changes to feature branch?

Push feature branch to remote This command pushes new-feature to the central repository (origin), and the -u flag adds it as a remote tracking branch. After setting up the tracking branch, git push can be invoked without any parameters to automatically push the new-feature branch to the central repository.

How do I create a new branch in GitLab?

Also if you go to a given issue page on gitlab, you should see a New Branch button which will automatically create a branch with a name of the form <issue-number>-issue-description. I was hoping to see a New Branch button, but either its not there or I can't find it. Do you know where it is placed? never mind found the create new branch.

How to create feature branches in remote Git hub or bit bucket?

To create feature branches in remote git hub or bit bucket we have to follow 3 steps those are After cloning your repository you can see your cloned repository. you can check with ls command. Here in my case it is decodingdevops. After entering your repository you can see you are in master branch. or you can check by using git branch command

How do I create a merge request in GitLab?

Also if you go to a given issue page on gitlab, you should see a New Branch button which will automatically create a branch with a name of the form <issue-number>-issue-description. On the Issue screen, you see a green button labeled "Create a merge request", with a down-arrow to its right.

How do I add a Test Branch to a git repository?

Create a new branch ( test-branch) against the feature branch ( release-x-y ): You should now be on a branch named test-branch. Make desired changes on the test-branch. git add . Navigate to the URL for your repository.


2 Answers

Make sure you are logged in to GitLab, as a owner/collaborator of the repository.
And of course, I assume you are using GitLab 8.6+, since that button was introduced in 8.6 (issue 3886).

Check if you see (on the Issue screen), a green button labeled "Create a merge request", with a down-arrow to its right.
That would be dropbox which includes the "Create Branch" option.

Create MR

An alternative would be locally (in your local clone) to create a branch named "<issue-number>-issue-description" and push it to GitLab: that would create and associate that branch to the issue.


Plus, with GitLab 15.0 (May 2022)

Internal notes

In many cases, organizations want to keep issues and epics public, but apply stricter governance to conversations within them. For example, when using GitLab issues as part of Service Desk workflows, organizations may want to make core details about an issue public, but not to expose customer-specific confidential data broadly.

With internal notes, you can redact discussions with internal or customer data that should only be visible to certain users, while keeping the core details about an issue public. Internal notes in issues or epics can only be seen by the issue author, assignee, and group or project members with at least the Reporter role.

Thanks @leetickett for collaborating with our team on this feature!

https://about.gitlab.com/images/15_0/add_internal_note_v15_0.png -- Internal notes

See Documentation and Epic.

like image 156
VonC Avatar answered Oct 13 '22 16:10

VonC


answering myself: in my case, the issues was created from a defect reported by github application security analysis CI run, and it is automatically marked as 'confidential', and for confidential issue, by default, there is no action available to create merge request and feature request.

in order to enable MR, I had to edit the 'confidentiality' label to toggle it off.

like image 24
sqr Avatar answered Oct 13 '22 17:10

sqr