Fatal Bug: MinGit on `Busybox` panics when pushing

[emmettlu]

Existing issues matching what you're seeing

• I was not able to find an open or closed issue matching what I'm seeing

Git for Windows version

~> git version --build-options
git version 2.53.0.windows.1
cpu: x86_64
built from commit: a5512bdee37ed7142c233d21e2d347ffc4860ff3
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
rust: disabled
feature: fsmonitor--daemon
gettext: enabled
libcurl: 8.18.0
OpenSSL: OpenSSL 3.5.5 27 Jan 2026
zlib: 1.3.1
SHA-1: SHA1_DC
SHA-256: SHA256_BLK
default-ref-format: files
default-hash: sha1

Windows version

Windows 10

Windows CPU architecture

x86_64 (64-bit)

Additional Windows version information

Microsoft Windows [Version 10.0.19044.6937]

Options set during installation

I use the zip archive so no `install-options.txt` file

Other interesting things

~> git push
-c: applet not found
bash: can't create /dev/tty: nonexistent directory
error: failed to execute prompt script (exit code 1)
fatal: could not read Username for 'https://github.com': No such file or directory

Terminal/shell

nushell & cmd & pwsh all exist this issue

Commands that trigger the issue

Just simply exec:

git push



~> git push
-c: applet not found
bash: can't create /dev/tty: nonexistent directory
error: failed to execute prompt script (exit code 1)
fatal: could not read Username for 'https://github.com': No such file or directory

Expected behaviour

Success

Actual behaviour

-c: applet not found
bash: can't create /dev/tty: nonexistent directory
error: failed to execute prompt script (exit code 1)
fatal: could not read Username for 'https://github.com': No such file or directory

Repository

No response

[emmettlu]

Note: No this issue for MinGit on Busybox that version 2.43 and earlier

[dscho]

@emmettlu Two notes. First of all, BusyBox based variant of MinGit is still experimental, and I'm really, really close to dropping it altogether because it's just not robust and it won't be robust ever because the BusyBox-w32 maintainer does not even accept CI builds, which reduced my confidence in that project rather dramatically.

Second, /dev/tty looks like it's asking for username and password. How did that work before? Are you sure that nothing changed in your setup? And that the credential helper, for example, is maybe no longer configured?