Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem create new feature with subfolder #94

Open
ferndem opened this issue Mar 17, 2020 · 5 comments
Open

Problem create new feature with subfolder #94

ferndem opened this issue Mar 17, 2020 · 5 comments
Labels

Comments

@ferndem
Copy link

ferndem commented Mar 17, 2020

I have a problem when create a new feature with subfolder, ex: "folder1"/"feature-name"

When I run command from prompt
git flow feature start "folder1"/"feature-name"

the correct branch is created.
If i create feature from plugin it create only "feature-name" branch

@ferndem ferndem changed the title Problema create new feature with subfolder Problem create new feature with subfolder Mar 17, 2020
@jakobehn
Copy link
Owner

jakobehn commented Jan 5, 2022

Really late here, but I can't reproduce this problem. When creating a new feature called feature/new-feature, it gets created correctly:

image

@ferndem
Copy link
Author

ferndem commented Jan 5, 2022

The problem is when using the GitFlow plugin and selecting "Start Feature"

image

@jakobehn
Copy link
Owner

jakobehn commented Jan 5, 2022

Yes, I know. That's what I did in the example above. the branch get created correctly, however the extension only shows the end name of the branch, maybe that is what you are referring to?

image

@ferndem
Copy link
Author

ferndem commented Jan 5, 2022

The problem is if I insert a subfolder that is:
fd/new-feature

image

create just "new-feature" and not "fd/new-feature"

image

@jakobehn
Copy link
Owner

jakobehn commented Jan 6, 2022

It actually creates the correct branch (fd/new-feature in your case), you can see that in the list of branches.
However the extension only shows the name of the branch. so that is a bug. I'll mark this as a bug and will fix it

@jakobehn jakobehn added the bug label Jan 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants