<!-- First and foremost, we’d like to thank you for taking the time to contribute to our project. Before submitting your issue, please follow these steps: 1. Familiarize yourself with our contributing guide: * https://github.com/desktop/desktop/blob/development/.github/CONTRIBUTING.md#contributing-to-github-desktop 2. Check if your issue (and sometimes workaround) is in the known-issues doc: * https://github.com/desktop/desktop/blob/development/docs/known-issues.md 3. Make sure your issue isn’t a duplicate of another issue 4. If you have made it to this step, go ahead and fill out the template below --> ## Description <!-- Provide a detailed description of the behavior you're seeing or the behavior you'd like to see **below** this comment. --> ## Version <!-- Place the version of GitHub Desktop you have installed **below** this comment. This is displayed under the 'About GitHub Desktop' menu item. If you are running from source, include the commit by running `git rev-parse HEAD` from the local repository. --> * GitHub Desktop: 1.6.0 <!-- Place the version of your operating system **below** this comment. The operating system you are running on may also help with reproducing the issue. If you are on macOS, launch 'About This Mac' and write down the OS version listed. If you are on Windows, open 'Command Prompt' and attach the output of this command: 'cmd /c ver' --> * Operating system: osx 10.14 ## Steps to Reproduce <!-- List the steps to reproduce your issue **below** this comment ex, 1. `step 1` 2. `step 2` 3. `and so on…` --> 1. click on changed file 2. click on another changed file ### Expected Behavior <!-- What you expected to happen --> smooth change of displayed file in patch subwindow ### Actual Behavior <!-- What actually happens --> "No local changes" window opens and disappear before every file change. ## Additional Information <!-- Place any additional information, configuration, or data that might be necessary to reproduce the issue **below** this comment. If you have screen shots or gifs that demonstrate the issue, please include them. If the issue involves a specific public repository, including the information about it will make it easier to recreate the issue. If you are dealing with a performance issue or regression, attaching a Performance profile of the task will help the developers understand the runtime behavior of the application on your machine. https://github.com/desktop/desktop/blob/development/docs/contributing/timeline-profile.md --> 