Do not commit unstaged changes for tracked files

[LPeter1997]

I don't know what I'm doing wrong, but I stage some files:

Then press c c to commit and...

The unstaged file appears! I've got burned by this before realizing for some reason this is some default behavior. Why is this happening? Can it be set up to not be the default behavior in case it's passing --all or something to the commit command?

[CKolkey]

That's... Odd. On the status buffer you can hit $ to see the git history. Tab to expand each entry. Maybe there's something there?

[LPeter1997]

I've tried on a blank repo and it worked perfectly, as expected. Then I went back to the project that had the issue.
As a test staged a single file:

The UI shows a single file staged and only that single diff BUT the summary shows all tracked files changed as to be added:

After commit, only the untracked file stays, rest of the changes went into the commit:

This is the history for the entry:

I've triple checked, no hooks set up for my repo, it should differ in essentially nothing compared to the blank one.

[CKolkey]

For debugging sake, if you run 'git commit' from the command line, does it similarly stage all those unstaged files?

[LPeter1997]

git commit works as expected. I've also tried lazygit both with and without NVim integration and they worked as expected. Weird.

[CKolkey]

And just to confirm, the "--all" flag in the commit popup is not set?

[LPeter1997]

No, it is not

[LPeter1997]

One thing I noticed, when I press c the first time, this pops up:

I assume this is the options that will be used by the commit and ˙--all˙ is already there for some reason