This repository was archived by the owner on Dec 15, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
v0.21.0-0 QA Review #1752
Description
Here are all the PRs going out in this release. Let's test them.
I'm excluding PRs that only touch docs or tests, since we had a few of those.
- [n/a] Add some instrumentation #1744 Add some instrumentation for context menu items
- change 'current' to 'checked out' #1731 change 'current' to 'checked out')
- [reverted] Feature: Add commit template support #1713 Feature: Add commit template support
- Fixed merged commit text #1711 Fix merged commit text on GitHub tab
- open Git pane when merge conflicts are present #1709 Open Git pane when merge conflicts are present.
- Fix: handle branch names mismatch #1708 Fix: handle branch names mismatch
- discoverability improvements #1704 Discoverability improvements
- Move "Undo Discard" button behind context menu #1702 Move "Undo Discard" button behind context menu
- [n/a] Add metrics collection for opening issueish in pane or browser #1694 Add metrics collection for opening issueish in pane or browser
- [n/a] Add metrics collection for committing partial changes, undoing the last commit, and opening an expanded commit msg editor #1685 Add metrics collection for committing partial changes, undoing the last commit, and opening an expanded commit msg editor
- Add tabs for issueish panel items #1684 Add tabs and commit list to GitHub pane
Activity
kuychaco commentedon Oct 22, 2018
For #1713 the commit message contents do not update when a merge conflict is initiated (expectation is that the merge conflict message would show up), or when the merge is aborted (expectation is that commit message template gets displayed). Note that these need not be fixed before the release.
annthurium commentedon Oct 22, 2018
@kuychaco I also noticed that #1713, if you delete all the text in the commit message box, it stays deleted until Atom window is refreshed. That might be something we want to address in the future but I don't think it's a release blocker.
kuychaco commentedon Oct 23, 2018
Ended up reverting #1713. We'll fix the regression associated with it and get it into the next release
@annthurium mind providing repro steps for this? Not quite sure what you mean