Staging files leaves blank Unstaged Changes tabs that then have to be closed

[wesinator]

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

Double clicking files in Git tab to stage changes, atom leaves empty Unstaged Changes tabs open for each file, that then have to be closed.

Steps to Reproduce

1. Project open with multiple unstaged changes files
2. Git tab, double click several files to stage

or

1. single click file to stage
2. Click Stage Changes button

Expected behavior:
Closes the git preview tabs after staging

Actual behavior:
Clicking/staging each file opens "Unstaged Changes" tab that stays open and has to be closed manually.
this is an annoyance when selecting a number of files for staging

at the end the user has to go back through and close the opened Unstaged changes tabs.

Reproduces how often: always

Versions

macOS 10.14.6

Atom    : 1.41.0
Electron: 4.2.7
Chrome  : 69.0.3497.128
Node    : 10.11.0
apm  2.4.3
npm  6.2.0
node 10.2.1 x64
atom 1.41.0
python 2.7.16
git 2.24.0

Additional Information

[darangi]

Thanks for contributing!

All new issues now require steps to reproduce (also called "repro steps") the problem or the behavior you wish to see in Atom. We do this so we can be certain that we are understanding what it is you're describing and don't prematurely close the issue or implement the wrong feature. If you need help writing detailed repro steps, please see the How Can I Contribute? section of the Atom CONTRTIBUTING guide.

[wesinator]

Thanks for contributing!

All new issues now require steps to reproduce (also called "repro steps") the problem or the behavior you wish to see in Atom. We do this so we can be certain that we are understanding what it is you're describing and don't prematurely close the issue or implement the wrong feature. If you need help writing detailed repro steps, please see the How Can I Contribute? section of the Atom CONTRTIBUTING guide.

Yes, I have steps to reproduce section, right under the image.