Would be useful if cherry-picker messages were more prominent
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 65
- Forks
- 47
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
As people have learned I am not always the most observant person in the world. My initial attempts to use cherry-picker were complicated by the fact that I paid attention to messages from git cherry-pick, not cherry-picker's own messages. It would be nice if the message sources were better distinguished, either by dimming the messages from git cherry-pick or by coloring the messages from cherry-picker.
If you think something like this would be useful, I could work on a PR. It seems that any desired changes would be straightforward, as current console output already uses click.echo().
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 by locating cherry-picker's console output that uses click.echo(), then compare its messages with the git cherry-pick output described in the issue. Done means cherry-picker messages are visibly distinguishable from git cherry-pick messages, with coverage for the relevant output paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100