Streamline use of amend feature
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 171
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 10
Description
Related to #426, which is to find ways to improve the UX of the amend feature.
I use amend a zillion times a day, and to hunt for it in the menu takes time.
Look at some screenshots here to see how gitkraken does it. As you see on the bottom right, there is the "Amend" checkbox. When you click it, it (1) automatically populates the commit message with the message from the previous commit, and (2) changes the button from "Commit" to "Amend Previous Commit".
Something similar could be done in the gittyup "commit panel" (unsure what it's called?), as seen here in the top right; if a "Amend" checkbox is added there, then the text could show the previous message and the "Commit" button could be changed to "Amend":
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
Start at the Gittyup commit panel and inspect the existing amend action. Compare the requested checkbox behavior with the current commit flow: showing the previous message and changing the button label when amend is selected. Done means amend is readily available in the panel and both states behave as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, git
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100