You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't understand this change that was made now so that the local branch name is not generated anymore. It seems like remote and local branch names are now different which is really confusing.
For example the local branch name seems to be "Lane" but there is a different remote branch name and they are not synced.
I feel that this is creating a bit of overhead for creating VB since I need to come up with local branch names manually. Before it was super easy and this is like the killer feature of GB
write some code
press generate branch name
press generate commit message
create PR
Now there seem to be more steps and clicks.
Many thanks
How to reproduce
No response
Expected behavior
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
Thanks a lot for letting us know, and thanks so much for describing how valuable this particular workflow was for you. And of course, I am sorry that this doesn't seem to work anymore.
Let me reel in @krlvi who probably knows all about this, maybe the workflow can be restored.
Version
0.13.4
Operating System
macOS
Distribution Method
dmg (Apple Silicon)
Describe the issue
Hello team!
I don't understand this change that was made now so that the local branch name is not generated anymore. It seems like remote and local branch names are now different which is really confusing.
For example the local branch name seems to be "Lane" but there is a different remote branch name and they are not synced.
I feel that this is creating a bit of overhead for creating VB since I need to come up with local branch names manually. Before it was super easy and this is like the killer feature of GB
Now there seem to be more steps and clicks.
Many thanks
How to reproduce
No response
Expected behavior
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: