Script file contents added to .bash_history

[jimzat]

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 2.25.0.windows.1
cpu: x86_64
built from commit: 7c71c859c97853ed057da5cbab12f3c13b5554df
sizeof-long: 4
sizeof-size_t: 8

   -   and -

git version 2.54.0.windows.1
cpu: x86_64
built from commit: 2b8a3ab140826ac423c2845ef81d4c6ac4f7bf3c
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.19.0
OpenSSL: OpenSSL 3.5.6 7 Apr 2026
zlib: 1.3.2
SHA-1: SHA1_DC
SHA-256: SHA256_BLK
default-ref-format: files
default-hash: sha1

Windows version

Windows 11

Windows CPU architecture

x86_64 (64-bit)

Additional Windows version information

Microsoft Windows [Version 10.0.26200.8246]
(c) Microsoft Corporation. All rights reserved.

Options set during installation

Defaults

Other interesting things

No response

Terminal/shell

bash

Commands that trigger the issue

When I launch a script from the command line no entries are made to .bash_history (as expected)

When I launch a script by launching it from Windows File Explorer, the script's contents get added to .bash_history

Expected behaviour

.bash_history should be left untouched when executing a script

Actual behaviour

When I launch a script by launching it from Windows File Explorer, the script's contents get added to .bash_history

Repository

No response

[becm]

This is standard behavior of bash.exe for being invoked with -i.

Skipping the argument for interactive mode will result in no history entry.
Not sure if there are (good) reasons to call bash this way for script execution.
Could just be to avoid deviation from the standard executable wrapper (-i only for invocation without arguments).