Create branch directly from issue UI #3441
-
NOTE: UPVOTE THIS PROPOSAL IF YOU LIKE ITrather than liking the discussion along with the discussion's "👍". PROPOSALWrite-up by https://github.com/krnlde (originally at isaacs/github#1125) Coming from Jira [and @ajRiverav from Gitlab] [we] really miss the possibility to create a [feature|hotfix] branch that matches the current issue with its name and ID. I suggest to put this workflow in the sidebar of an issue where the Assignees, Labels and Milestones reside. The following workflow would be nice: Create an issue "My Example Issue" with id 42 |
Beta Was this translation helpful? Give feedback.
Replies: 17 comments 70 replies
-
Just saying that this issue has 1533 likes! It is by far the most demanded feature request on github.com, will the company listen to its userbase or continue ignoring us? |
Beta Was this translation helpful? Give feedback.
-
@ajRiverav At the top of your discussion description, could you write that folks should upvote the discussion along with the discussion's ":+1:" ? |
Beta Was this translation helpful? Give feedback.
-
Come on github! |
Beta Was this translation helpful? Give feedback.
-
It's currently possible to do this with GitHub Apps, but a native integration would be nice. |
Beta Was this translation helpful? Give feedback.
-
The original issue had 134 comments and 1547 thumbs up for this feature. I hope that would be considered as part of this feedback. |
Beta Was this translation helpful? Give feedback.
-
Started to use GH for setting up a good project management workflow and this feature would be really useful. The original issue as commented from @YuraYefymenko has lots of demand since 2017, please add! |
Beta Was this translation helpful? Give feedback.
-
It sounds like this isn't very important ... till you get used to this workflow (e.g. in jira/bitbucket), then you can't live without it. It helps the project keep consistent branch names. It helps ensure developers follow the desired process by making it the easiest. And of course it simply makes branches for issues quick to create. Please Github, make my life 27% better and implement this feature. |
Beta Was this translation helpful? Give feedback.
-
This already works really well in GitLab. It creates the branch and the Merge Request (in Draft status) with one click. I just went to find out how to do this in GitHub and was disappointed to find out it didn't exist and found my way to this discussion by clicking through unresolved past issues. |
Beta Was this translation helpful? Give feedback.
-
Hey y'all. This feedback space is currently reserved for GitHub Discussions only. However, I've passed this feedback along to our Issues team so they can take a look. |
Beta Was this translation helpful? Give feedback.
-
Come on github, lets do this 👍 |
Beta Was this translation helpful? Give feedback.
-
👋🏼 @krnlde @ajRiverav + everyone, thanks for the feedback here (and isaacs/github#1125)! Currently, this work is being prioritized internally. It will surface later on the public roadmap. Keep watching this space! |
Beta Was this translation helpful? Give feedback.
-
📣 Update: This product enhancement published yesterday on our public roadmap! You can now track the issue here. |
Beta Was this translation helpful? Give feedback.
-
So, it is currently in "Future" on roadmap, which means "not before q3 2022". Sounds like really complicated feature. |
Beta Was this translation helpful? Give feedback.
-
This feature could improve the productivity of my development team by using GitHub standard configuration. In turn, this will also improve the privacy of my private project because right now I have to share my private repository with 3rd party code only to achieve the desired productivity. Setting up a 3rd party solution is also a time-consuming task. I hope it's getting prioritized and developed soon. I see only wins for everyone from every angle. |
Beta Was this translation helpful? Give feedback.
-
Hi 👋 I hope everyone is doing well! We are currently working on adding the functionality to allow creating a branch for an issue. If anyone is interested in trying it out early, please let me no with a comment here and I'll enable it for you. |
Beta Was this translation helpful? Give feedback.
-
Nice work, Dan! While the PM position didn’t work out for me, I really enjoyed the conversation I had with you and Jason - it’s so cool to see this solution coming to fruition! 😊
Hope you had a great holiday break and happy 2022!
Cheers,
Elena
From: Daniel Adams ***@***.***>
Date: Friday, January 7, 2022 at 11:46 AM
To: github/feedback ***@***.***>
Cc: Elena Newton ***@***.***>, Manual ***@***.***>
Subject: Re: [github/feedback] Create branch directly from issue UI (Discussion #3441)
Enabled for all of the above. You will see a new section in issues called "Development" with a "Create a branch" button. If you are a member of the repo can create branches linked to the issue for that particular repo. There are a few rough edges we still have to resolve. However, please don't hesitate to leave any feedback here.
For anyone else who's not in yet, I'll have a look once a day and add you.
—
Reply to this email directly, view it on GitHub<#3441 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAXHWMP7CROCU7K3PBHSJ4DUU4YGVANCNFSM4YJHYBCQ>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
@dipree: Tried the beta. The flow feels natural and the branch creation is intuitive + does work :) . So far, it solves the issue I posted originally, which was about creating a branch from the browser. cc: @Bestra Issue 1
However, there was no PR created (at least it was not listed in the corresponding tab). Issue 2The "copy" button did not seem to work on latest (as of today) Safari. It only copies the branch name, which may be sufficient, I guess. ObservationIt's very nice that one can see all the "associated" branches created -> |
Beta Was this translation helpful? Give feedback.
📣 Update: This product enhancement published yesterday on our public roadmap! You can now track the issue here.