feat: adds branch command to unset upstream

[cdloh]

No description provided.

[kaste]

Ah, that's useful.

We actually have a command in the Command Palette to unset the tracking information for the checked out branch, that is gs_unset_tracking_information

GitSavvy/core/commands/branch.py

Lines 145 to 154 in 5aa2dfa

	class gs_unset_tracking_information(GsWindowCommand):
	defaults = {
	"branch": push.take_current_branch_name,
	}
	def run(self, branch):
	self.git("branch", branch, "--unset-upstream")
	self.window.status_message("Removed the upstream information for {}".format(branch))
	util.view.refresh_gitsavvy_interfaces(self.window)

Let's just delegate to that command. We do this quite often in this interface. Something among self.window.run_command.... Also probably check if the selected branch is a remote branch, e.g.

GitSavvy/core/interfaces/branch.py

Lines 481 to 485 in ca8605a

	def run(self, edit):
	if self.selected_branch.is_remote:
	flash(self.view, "Cannot configure remote branches.")
	return

and if it actually has upstream/tracking set.

[cdloh]

Thanks @kaste. I think I've implemented all of those changes.

I couldn't find any docs or relevant tests but happy to if I've missed something.

[kaste]

Excellent.

I usually don't have tests for these ... basically simple wrappers. Most logic is in the parent classes e.g. CommandForSingleBranch.

Actually, happy that this is such a simple diff/patch as well.

(I still need to fix these mypy errors; the latest mypy version got smarter and I did not pin the version here. 😬)

Let's roll.

[kaste]

🥁

[cdloh]

many thanks for maintaining the plugin @kaste! Not sure how much time I save with it weekly. All muscle memory now.

How long does package control take to pickup the new version?

[kaste]

It's a crawler... checks every 3 hours