[Bug]: Can't push on windows 10

[RomainBitard]

Describe the bug

I set up the plugin but I can't push on the remote branch. With a command line I can though (both cmd.exe and git bash)

Do you know how to solve this ?

Relevant errors (if available) from notifications or console (CTRL+SHIFT+I)

Cf bug.png

Steps to reproduce

Install the plugin and git on windows and try to push a new change

Expected Behavior

No response

Addition context

No response

Operating system

Windows

Installation Method

None

Plugin version

latest

[Vinzent03]

Did you follow the documentation?

[RomainBitard]

Yeah

On Sun, 16 Jul 2023, 23:32 Vinzent, @.***> wrote:

Did you follow the documentation https://publish.obsidian.md/git-doc/Authentication#HTTPS?

— Reply to this email directly, view it on GitHub https://github.com/denolehov/obsidian-git/issues/561#issuecomment-1637194719, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADKQOCXVVDPC5FFXBNPYLADXQRMX5ANCNFSM6AAAAAA2ME37XQ . You are receiving this because you authored the thread.Message ID: @.***>

[mike2ykme]

Reading the documentation I don't see where this is a supported feature on Windows. That said, git bash is a set of libraries written on top of Windows (reminds me of cygwin really) and you might be able to just setup some of those in your path and see if that works.

[RomainBitard]

Reading the documentation I don't see where this is a supported feature on Windows. That said, git bash is a set of libraries written on top of Windows (reminds me of cygwin really) and you might be able to just setup some of those in your path and see if that works.

Thanks for the reply, I said cmd.exe and git bash I know that git bash isn't mentioned on the documentation but I wondered if it was useful information

[tomfluff]

So I had the same issue and I did two things which got it solved (not sure which one is the actual solution, maybe both):

1. Make sure the SSH key is named id_[xxx] (not sure if that is actually important).
2. Follow these instructions to make sure ssh-agent starts for bash.

Hopefully this helps! Maybe try (2) first, I think that's the actual solution.