Skip to content

Conversation

@sergeibbb
Copy link
Member

Description

Solves #4353.

The problem was in incorrect handling of blank "reachable stashes" result. In some cases the set of unreachable wasn't cleared so undesired stashes and commits appeared in the view.

Checklist

  • I have followed the guidelines in the Contributing document
  • My changes follow the coding style of this project
  • My changes build without any errors or warnings
  • My changes have been formatted and linted
  • My changes include any required corresponding changes to the documentation (including CHANGELOG.md and README.md)
  • My changes have been rebased and squashed to the minimal number (typically 1) of relevant commits
  • My changes have a descriptive commit message with a short title, including a Fixes $XXX - or Closes #XXX - prefix to auto-close the issue that your PR addresses

@sergeibbb sergeibbb force-pushed the 4353-fix-stash-in-wrong-branch branch from d701b4b to ef6de00 Compare June 11, 2025 17:35
@d13 d13 merged commit bdb8200 into main Jun 11, 2025
3 checks passed
@sergeibbb sergeibbb deleted the 4353-fix-stash-in-wrong-branch branch June 12, 2025 10:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Switching the gitlens.views.repositories.showStashes on breaks the Branches tree

3 participants