You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
When "discard changes" is used, the local file is updated, but anything listening for a save event (like the remote sync pro package) needs to be manually triggered by saving again.
Motivation
If a discard changes to a repo, I need to manually save the file again to trigger remote sync pro to update the foreign copy. When discarding changes to a file or two, this is fine, but when using "Discard All Changes" I need to remember which files require updating.
Describe alternatives you've considered
Additional context
This is my first issue for atom, sorry if I didn't provide enough details or if this is caused by code in atom core or in the remote sync pro package instead, I'm not sure how events work in atom.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summary
When "discard changes" is used, the local file is updated, but anything listening for a save event (like the remote sync pro package) needs to be manually triggered by saving again.
Motivation
If a discard changes to a repo, I need to manually save the file again to trigger remote sync pro to update the foreign copy. When discarding changes to a file or two, this is fine, but when using "Discard All Changes" I need to remember which files require updating.
Describe alternatives you've considered
Additional context
This is my first issue for atom, sorry if I didn't provide enough details or if this is caused by code in atom core or in the remote sync pro package instead, I'm not sure how events work in atom.
The text was updated successfully, but these errors were encountered: