Replies
|
this is nice. but i would prefer like gitlab has it, that it creates both a branch and a PR for you. one of the things that annoys me a lot when working on github. i like to take notes about my work in the PR but on github i can't do that before i already have 1 commit on the branch, something which doesn't always happen so fast. |
|
It would be pretty awesome if it were possible to link an existing branch from another repository within the scope of the organization. Where I work there is a certain repository of tasks where it is not possible to link Pull Requests or Branches because the projects are done in another repository, this would be an excellent addition. |
|
Just noticed that when I do create a PR from the branch, it automatically links it to the issue and marks the issue for autoclosing when the PR is merged. This is something we don't want in our org so this is a bit annoying. E.g. we already have to write "for #123" in PRs instead of "fixes #123" to avoid the autoclosing, and this adds another thing we have to dodge. |
|
Not within the scope of this feature currently, but in the future it would be neat to see:
Great work guys |
|
I can't assign existing branch ( |
|
It would be great if we can configure some sort f regex when it comes to the naming convention of the branch as well as limit or unlimit the name length of the branch For example.
|
|
Could we get the option to move a projects story to the correct column when using the create branch feature? A story/issue is in the Todo column. Once the branch is created the story is then moved to the "In Progress" column. |
|
We'd like to see the ability to configure a default repository destination. We've got a two-repo structure for all projects to separate project management and source*. So for a ticket in the On a related note, being able to configure the default branch would also be nice. Something a bit more complex: configuring the default branch source (and branch name) based on labels.
|
|
Love the feature! But I think I ran into a bug? My issue title is something like " |
|
This is amazing, it working very good! But have a stranger behavior, when have " - " in name of issue, type "Product - Create Variants", in name of branch get 3 "-", type "52-produtos---create-variants" |
|
I like this feature, and it would be better if we can add the feature type to the branch name like |
|
Not sure if I'm allowed to post this again but I guess there will always be features not covered by the platform itself.
FD: I'm the author of that app. I think the current "Create a branch" functionality in the platform is a great starting point for most development workflows (and most likely sufficient for many projects), but if you're looking for more control please consider the Create Issue Branch App/Action. |
|
|
It would be great to see what's the branch you are branching off. |
|
Bug report with current behaviour: Current:
Expected: |
|
I'd like it to autoassign the issue to the branch creator if it currently had no assignee. I'm creating the branch meaning that i'm taking responsibility for that issue..... Some companies pre-assign issues, mine works on a self-service/assign-when-you-are-working-on-it basis. |
|
Brilliant! Was just looking at my Git workflow and wondered if this was a thing, and it – now – is! A couple of requests:
Last one, something like this (which I may throw into a Chrome extension at some point): let input = document.getElementById('branch-name')
input.value = input.value.replace(/^\d+/, s => {
while (s.length < 4) {
s = '0' + s
}
return s
})
input.addEventListener('input', e => {
// variables
const input = e.target
const value = input.value
const index = input.selectionStart
// update
input.value = value
.replace(/[- ]+/g, '-')
.replace(/^-|-$/g, '')
// fix cursor
input.setSelectionRange(index, index - (value.length - input.value.length))
}) |
|
I created a branch for an issue, even post deletion of this branch, I'm unable to create a new branch likewise. |
|
Thanks for this cool addition! However, I'm part of an organization where we all work in our own forks instead of the production repo. Currently, the "Repository destination" selector is quite useless, cause it always selects the main repo instead of the fork by default. It would be cool if it could remember the last selection. Furthermore, the selector shows many unrelated repositories but not my own fork. So even if remembering the last selection is considered a bad idea, a fork of the repo should always be shown on top of the selection list. |
|
I was very surprised that this new workflow closed my issue when I merged a related PR. This wasn't happening before. Compare the "old" workflow:
The new workflow:
(Note: In neither case I used the "closing keywords" in a PR description.) Auto-closing is often undesirable for us, for example, we have issues that require multiple PRs to be merged first, or sometimes more manual work is needed after a PR is merged. Fundamentally, I think that merely linking issues and PRs shouldn't be such a strong relation that merging a PR would close the issue. What I think would be better behavior:
GitHub's UI itself is a bit vague, for example, for issues with linked PRs, the UI says "merging PR |
|
Now we can create branches directly from with projects page, that is great. Small but annoying issue - "Branch source" dropdown search is not working. Steps to reproduce -
Result - Search does not filter out the branch Expectation - Search should filter out the branch |
|
I just stumbled upon this feature after having created and pushed a bugfix branch; it would be nice if there was also a way to link an existing branch. |









In an issue, you can now create a branch for that issue and start work right away. In the sidebar of an issue, branches connected to the issue are shown in the "Development" section, which has replaced "Linked pull requests". When you create a pull request for one of these branches, it is automatically linked to the issue. You can learn more about the functionality in our documentation.
Addresses github/roadmap#218 on our public roadmap.
We can't wait for you to try it out! Let us know what you think here in Discussions.