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 Mar 3, 2023. It is now read-only.
I ran git mv lib src in my Terminal. I happened to have a file in lib (pathology-view.coffee) open in a buffer. A few minutes later I reloaded Atom. It asked me if I wanted to save my modifications to pathology-view.coffee, so I said sure. Now I have a lib and a src folder. I know we've talked this behavior to death from the perspective of branch changes, etc, but it continues to get in my way pretty frequently.
User: jbarnette
Atom Version: 3053c4a
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Atom/3053c4a Safari/537.36
The text was updated successfully, but these errors were encountered:
This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!
lockbot
locked as resolved and limited conversation to collaborators
Jan 27, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I ran
git mv lib src
in my Terminal. I happened to have a file in lib (pathology-view.coffee) open in a buffer. A few minutes later I reloaded Atom. It asked me if I wanted to save my modifications to pathology-view.coffee, so I said sure. Now I have alib
and asrc
folder. I know we've talked this behavior to death from the perspective of branch changes, etc, but it continues to get in my way pretty frequently.User: jbarnette
Atom Version: 3053c4a
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Atom/3053c4a Safari/537.36
The text was updated successfully, but these errors were encountered: