Showing binary differences where git is able to create diff
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 171
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 10
Description
Instead of showing only the icon of the binary. For merges, just the image as below can be shown, because git is not able to resolve such conflicts
Gittyup v1.1.1
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
No source file or test is named. Start by reproducing the issue in Gittyup with a binary diff and a binary merge conflict, then trace the existing binary-file display entry point. Done means binary differences are shown when Git can produce them, while merge conflicts display the requested image instead of only the binary icon.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, git
- Domain
- desktop, devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100