Use `dunk` for snazzy diff output
Open
Nobody has claimed this yet.
command line tools
low-priority
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
This looks like a super nice library to use to format the diff outputs we show when updating modules: https://twitter.com/_darrenburns/status/1510350016623394817
Contributor guide
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 file, test, or entry point is named. Start by locating the code that formats diff output when modules are updated, then review the linked dunk library and determine the integration scope; done means those update diffs use dunk's formatting consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100