Philippe Miossec
Philippe Miossec
Could that help? If GitExtensions requests some developers licenses maybe... https://docs.github.com/en/developers/overview/github-developer-program
@valekseev-fls It's due to the update of dotnet framework that just been released provided through Windows update. THe workaround is indeed to restart GitExtensions.
> Can you read the configuration for a repo and get the length of the sha? Somewhat possible with `git rev-parse --show-object-format`: * https://git-scm.com/docs/git-rev-parse/2.44.0#Documentation/git-rev-parse.txt---show-object-formatstorageinputoutput * https://stackoverflow.com/a/65874596/717372 * https://git-scm.com/docs/hash-function-transition#_detailed_design
FYI, from what i understand from this article ( https://www.phoronix.com/news/Git-2.46-rc0-Released ), next version will start to initialize new repos with sha256... If that's true, I think we will see error...
Reading it again, you're right. I was mistaken by: >Git 2.46-rc0 is also no longer setting SHA1 as the default object hash type when initializing a repository. But it seems...
It took me a time to understand the feature request... This request is about the VisualStudio integration  It probably should be moved to : https://github.com/gitextensions/gitextensions.vsix/issues
Have a look at the changes I have pushed. I think that fixes some issues...
>In general I am not fond of moving files around, it breaks patches and history. Yes, we can't say that Git (or GitExtensions) is handling move and rename perfectly. Crossing...
> "eng" is short for "engineering". That's a convention in the dotnet/* repos and many other MS internal repos. So for me that's kind of natural... Do you have any...
> Git is able to automatically resolve the MC when rebasing They are some cases where Git is not good: * new files added in commits rebased. Because Git handling...