Description: When attempting to commit a file partially by staging specific lines or hunks, the expectation is that unstaged parts of the file remain unstaged. However, when committing the staged changes, all changes (both staged and unstaged) are committed. This behavior was not observed in earlier versions and seems to be a regression.

Version: 4.2.10 (269) and some recent versions (exact version of regression is unknown, but it worked correctly in the past).

Steps to Reproduce:

1. Make changes to a file (ensure the changes span more than 2 lines).

1. Stage one line of code or a specific hunk, leaving the other changes unstaged.

1. Commit the staged changes.

1. Check the status of the unstaged changes.

Expected Result: Unstaged changes should remain unstaged after committing the staged changes.

Actual Result: Unstaged changes are also committed along with the staged changes.

Notes:

• This issue was observed starting with version 4.2.10 (269), but the exact version where the problem began is unknown.

• This functionality previously worked as expected in older versions.