-
Notifications
You must be signed in to change notification settings - Fork 30.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show readonly filename decoration after revert that also resets mtime (fix #221014) #221023
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I like this. Two feedback:
- I think we can also apply the
locked
property alongsidereadonly
which is for when a file system marked a file as not writeable - could we have 2 tests to test this if possible per text file model and stored file working copy?
I have added handling for |
Any chance of merging this for July? |
@bpasero can this be milestoned for August? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
This PR fixes #221014.
A "reserve-before-edit" type of SCM tool can result in a FileSystemProvider
stat
result with both an earliermtime
and a changed (set)FilePermission.readonly
bit inpermissions
. VS Code was ignoring this, leaving the reverted document editable.