1

I'm receiving the following error trying to push to the Github repo. I'm working on windows, repo is on GitHub.

Looks like some problem with the Credentials Manager, because after the error message, credentials is being requested again, and I can push my changes anyway, but the error is really annoying.

I know that GitHub no longer support TLS 1.0 and 1.1, only 1.2, that's why I updated to last version Git for Windows:

git --version
git version 2.17.0.windows.1

However it does not help much

UPDATE: Detailed STR

git commit --all -m"#ISSUE-123 Rename example dirs; added command-line handlers"
22 files changed, 501 insertions(+), 7 deletions(-)
git push https://<my_username>@github.com/<my_repo>.git #ISSUE-123
fatal: ArgumentNullException encountered.
Value cannot be null.
Parameter name: path

Of course, path and username are 100% correct

3 Answers3

5

I solved the issue, looks like hard-to-reproduce problem with Git Credential Manager. First, I reinstalled Git and de-selected "Git Credential Manager for Windows" checkbox. Then I installed Credential Manager separately from the Git page. Everything works fine now. Hope will be fixed in the next version for Windows

4

To improve Yuri S. Cherkasov solution, you can directly remove "Git Credential Manager for Windows" by running :

git config --edit --system

And remove the following line :

helper = manager

Credits to jez from this post : How to disable Git Credential Manager for Windows?

bossno
  • 587
  • 6
  • 12
0

Bash treated the hash # as start of comment:

git push https://<my_username>@github.com/<my_repo>.git "#ISSUE-123"

Quote the string that contains the hash and the problem should go.

It doesn't seem to be a common practice to have hashes in branch names, however.

iBug
  • 35,554
  • 7
  • 89
  • 134
  • Never had any issue with the hash before. Quotation does not help –  May 14 '18 at 12:57
  • See the questions, I'm under Windows, hash does not treated as a comment –  May 14 '18 at 13:19