Keep file diff open after commit, if it still has changes
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 171
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 10
Description
Reproduction:
- stage hunks of some file
- either amend or commit
What I'd expect:
- if the file diff that was open has no more changes, gittyup should jump to the first file of the "unstaged files" list
- if the file diff that was open has more changes, gittyup should keep that file open
What actually happens:
After the commit gittyup jumps to the first file of the "unstaged files" list. Which is always frustrating when you are still working on the original file.
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 issue by staging hunks in one file, then committing or amending, and trace the commit flow that refreshes the unstaged-files list and selected diff. Done means the current file remains open when it still has changes, while a file with no remaining changes moves to the first unstaged file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100