Using non-standard keyboard layouts on Windows makes it impossible to get passphrase correct to deploy

[r134x7]

I will write out the exact circumstances that causes this issue to occur so that anyone else can replicate it to test and show that it doesn't work.

I am using Windows 10, I do not use the QWERTY keyboard layout. I use the Engram keyboard layout, the link to download the layout is https://keyman.com/keyboards/engram

I am using Git Bash and when I use it for pushing to GitHub there is never an issue with entering the passphrase regardless of the keyboard layout I use.

When I am using the Engram Keyboard Layout, here is the (orange) icon on the windows taskbar indicating that Keyman is running the Engram Keyboard Layout:

When I am using gh-pages to push the react app build to the gh-pages branch what will happen is: it does the predeploy and then the deploy scripts and then, a window pops up saying "Git for Windows" and it has a password input asking for me to enter my passphrase. I have entered my passphrase in Engram keyboard layout, in QWERTY keyboard layout and I even copy-pasted my passphrase and yet I fail all three attempts to enter my passphrase that I get permission denied.

I tried the exact same things over and over again, and then I noticed that something changes when that "Git for Windows" window pops up, the keyboard layout on the taskbar changes to QWERTY automatically.

The problem is, despite knowing that happens meaning I have to enter the password is QWERTY (which I had already done repeatedly before that) I still failed all three passphrase attempts. Note: After failing the passphrase attempts, and the "Git for Windows" pop-up disappears, the keyboard layout does revert back to Engram automatically.

So then I tried something, I changed from Engram to QWERTY manually before doing a gh-pages deploy again. I deployed, the "Git for Windows" pop-up appeared again for entering the passphrase, I entered it in QWERTY (because again, I cannot see the password at all regardless of what I type or paste into the input field) and suddenly it took a little longer for the window to reappear after submitting once. I then entered the passphrase again on the second attempt and then finally, the pop-up disappeared and the Git Bash terminal said my deploy has been published.

I am used to entering passwords in QWERTY on password fields in forms on websites because whatever you type in will default to QWERTY unless you make the password field visible. Not only that, I can at least type out my password in Engram somewhere else and copy and paste it into the password field of a form on a webpage and it will work. The issue is that this bug that occurred on the "Git for Windows" pop-up did not follow that same logic, something caused this bug to occur while not using a QWERTY keyboard layout regardless of typing the passphrase in QWERTY.