Overly aggressive disabling of branching
See original GitHub issueThanks for all the work on this extension, it’s coming along nicely!
I often will make uncommited changes to a repository, then later decide I want to commit them in a new branch. Git allows one to checkout a new branch when there are uncommited changes (or even staged changes), and then proceed as normal. However, when I try that in the UI, I get an error message saying
Creating new branch disabled
You have staged changes in current branch. Please commit / discard them before creating a new branch.
Is this disabling of branching really necessary? It’s not a hard git requirement (also, note that the error message is incorrect if there are unstaged changes). Apologies if there is already an issue discussing this, I didn’t find one after a quick search.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Cisco Wireless LAN Controller Configuration Guide, Release 7.4
To enable or disable aggressive load balancing on specific WLANs, do the following: Choose WLANs > WLAN ID. The WLANs > Edit page...
Read more >Aggressive tax planning - OECD
The work is informed by a library of over 400 aggressive tax planning schemes stored ... 27/07/2017 - BEPS: Neutralising the tax effects...
Read more >Disability and Safety: Aggressive Behavior and Violence - CDC
Most children with developmental disabilities are not any more violent or aggressive than other children. However, some children may feel a lot of...
Read more >Configure IPSec VPN Phase 1 Settings
For a branch office VPN that uses IKEv1, the Phase 1 exchange can use Main Mode or Aggressive Mode. The mode determines the...
Read more >git-gc Documentation - Git
--aggressive. Usually git gc runs very quickly while providing good disk space utilization and performance. · --auto. With this option, git gc checks...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
As a power user, I hate unnecessary dialogs that you have to click through so I’d very much appreciate a setting to disable that.
So let’s go for prompting a warning dialog and not using a setting. This is simple and does not require advanced users to know about a setting. users tend to go to the documentation or the git repository rather that looking for settings.