Popping stashed change from stash view softlocks the commit view.
Open
Nobody has claimed this yet.
bug
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 171
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 10
Description
When the last stashed change is popped from the stack, it leaves the UI in a softlocked state that prevents one from getting back to the commits of the remaining branch. The video below depicts the flow of this on a test repo with only one branch.
- An unstaged change is pushed into the stash.
- The view is changed to the stash view.
- In this view, that one stash is popped from the stack.
- Observe how the UI does not return to the main branch and instead is displaying invalid information.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the flow in the Gittyup stash view using a test repository with one branch: stash one unstaged change, open the stash view, and pop the only stash. Trace the view transition after the stash is removed; done means the UI returns to the main branch and the commit view remains usable with valid information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, git
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100