Why is delete branch forced (-D) by default

[andylaw]

I'm new to SourceGit, but not to Git. I'm putting together a short course for local users at my place of work. I just got on to creating and deleting branches.

It was a great shock to discover that I can delete leading branches without having to confirm a force. That seems bizarre to me. Surely such a destructive action should be an option, not a default. Am I missing something?

[love-linger]

Does not SourceGit show the Delete Branch popup to ask your confirmation?

[andylaw]

SourceTree requires confirmation of destructive deletes though. Just because other tools allow a naive/careless user to shoot themselves in the foot, doesn't mean that SourceGit should

[love-linger]

I've pushed a new commit that rewrites the branch deleting feature.

• Add a Force delete even if it contains unmerged commit(s) option
• Remove the Also delete remote tracking branch <upstream> option. Instead, after successfully deleting the local branch, ask user for deleting remote branch when
  • The local branch has a valid tracking remote branch
  • The name of the tracking remote branch is same with the local branch
• For Delete Multiple Branches popup, -d is used instead of -D

[andylaw]

I'll need to wait until someone builds a Mac version of that for me to view it, else try to find access to build my own copy on a Windows box. Thanks.

[gadfly3173]

I'll need to wait until someone builds a Mac version of that for me to view it, else try to find access to build my own copy on a Windows box. Thanks.

You can download in Github Actions , like https://github.com/sourcegit-scm/sourcegit/actions/runs/28285219620

[andylaw]

Sadly, my work-managed laptop won't allow unsigned code to run :(