dpjohnst
commented
6 days ago Hi @schmiidt,
Thanks for reaching out and sorry to hear you've run into this issue.
To investigate this further, would you mind sharing your Sublime Merge Debug Information when you have a spare moment? It can be collected with the following steps:
- Open Sublime Merge
- Open the repository where the bug occurs
- Navigate to
Help > Debug Informationvia the application menu - Before sharing, please redact any information that's sensitive such as file paths, git user information, remote URLs etc.
In particular, I'd be interested in seeing the git config portion of the debug information if you'd mind sharing this.
Many thanks, - Dylan from Sublime HQ
schmiidt
Version info
Description
I upgraded Sublime Merge this morning from build 2099 to 2100. After the upgrade, several files appeared as modified in Sublime Merge, but when I run git status (version 2.42.0) from the command line, they do not show as modified. Sublime Merge lists these files as deleted, even though they are still present in the file system with all their content intact. The affected files are plain text files, as far as I can tell, and they are all located in the same directories within a large monorepo.
Curiously, Sublime Text does not show these files as modified either, so there seems to be a discrepancy between the modified files shown by Sublime Merge and Sublime Text.
Steps to reproduce
I guess you need access to my git repository to reproduce this since I did nothing else other than upgrading Sublime Merge from build 2099 to 2100.
Expected behavior
The expected behavior is to show the files as not modified.
Debug Information
Here is a list of some of the files that show up as modified in Sublime Merge but not in git or Sublime Text.
The above files are shown as modified in Sublime Merge but not in git and Sublime Text.
Please do not hesitate to contact me if you need more information. I will be available for a joint debug session as well if you need to guide me through some further debugging of the issue.