Jay Asbury

https://github.blog/2022-04-12-git-security-vulnerability-announced/

In the future just use the copy button on the about dialog and then paste in issue.

You can do that. However, that negates the security fix that was put in place. https://github.blog/2022-04-12-git-security-vulnerability-announced/

> @vbjay > > You can do that. However, that negates the security fix that was put in place. https://github.blog/2022-04-12-git-security-vulnerability-announced/ > > if I don't do this my gits are...

Run ```bash git ls-files -z --unmerged ``` in a git bash in your repo folder or console tab in ge. Does it suggest --add-safe-directory in the output? https://github.blog/2022-04-12-git-security-vulnerability-announced/

Did you fork the gitextensions repo first? Set up your local repo to have 2 remotes. - origin is your fork URL - upstream is gitextensions/gitextensions Do a fetch all...

https://github.com/gitextensions/gitextensions/blob/master/CONTRIBUTING.md

I'll see if I can post an issue for git for windows.

Sure. I still thought it was a good idea to document the issue. On Sat, Sep 8, 2018, 7:56 PM Gerhard Olsson wrote: > I rather see the warning in...

Since our application takes over and runs git commands and it isn't going to get fixed any time soon, I think warning the users is a valid response.