Stefan Haller

This only confirms that the Push command is still blocking on the global sync mutex (but we know this already from the logs); it will only log its command once...

I don't know; do a bit of research, perhaps? I'm not very experienced with networking stuff. A very cursory google search turned up [this](https://medium.com/@liwp.stephen/solve-the-problem-git-fetch-origin-hangs-4b54146af2da), which sounds somewhat related. I suppose...

Depends on how you look at it. It does have to do with lazygit insofar as its management of the global sync mutex goes, and how it assumes that no...

Of course, there's also the possibility that the `git fetch` process is actually fine, and it only hangs because of the way we poll for its completion in go. But...

I'm confused. Lazygit is not supposed to open an editor when creating a tag. It opens its own message panel which lets you enter the tag name, and optionally a...

> The command was > > ``` > git tag -- > ``` I find this hard to believe. No tag name? Lazygit uses the command `git tag -- `...

> * From the diff window, be able to switch between diff mode and full-content mode When I have this need I like to use `git difftool` as a workaround...

This sounds more like a bug than an enhancement request. However, I just did a quick test and the command worked correctly for me: it created one stash, didn't pop...

It's a known problem, this step currently always fails for PRs created from a fork.

Duplicate of #2589. The conclusion in that issue is that removing `{{line}}` support from the `o` command was by design, and we won't change that for now. However, we will...