Open lonkelle opened 1 year ago
I've transferred this issue to Sublime Merge as it's a git issue common between the two.
Hi @lonkelle,
Thanks for reporting this issue - I'll be investigating this further. So far I haven't been able to reproduce this issue on my end, so something unique must be happening here.
Could you confirm whether the Git CLI reports any changes? e.g. run git status
in the repository directory on the command line.
As Sublime Merge uses the same Git reading library as Sublime Text, would you mind installing Sublime Merge for the purposes of debugging this issue? Sublime Merge has detailed debug information you can collect to narrow down what's going on. If you're happy to install it to debug this issue further it can be found here: https://www.sublimemerge.com/download
Once installed, if you could open the repository in question and select Help > Debug Information
from the application menu and share the information here. Before sharing, please redact any information you feel is sensitive such as file paths, Git user information, and repository URLs.
Kind regards, - Dylan from Sublime HQ
Description of the bug
This command forces GIT to assume certain files are unchanged always. Sublime still sees them as changed despite GitHub Desktop noticing instantly that it should no longer monitor them.
Steps to reproduce
Expected behavior
Sublime should only show a blue circle "changed indicator" on the individual files (or ignore entirely) - especially not the ENTIRE folder being marked as having project changes when it actually doesn't.
Actual behavior
Sublime marks the entire project folder as change with a blue icon and
git update-index --assume-unchanged
files are treated just like all other files int hat regard.Sublime Text build number
4143
Operating system & version
macOS 10.13.1
(Linux) Desktop environment and/or window manager
No response
Additional information
No response
OpenGL context information
No response