Loss of title and description when doing `cherry_picker --continue`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 65
- Forks
- 47
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
Maybe I'm doing something wrong, but when I have used cherry_picker --continue I inevitably lose the title and description I would have ended up with had there not been any merge conflict. Not sure if there's any way to prevent that or to output what the message would have been so I can copy-and-paste it into the eventual PR?
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 reproducing the cherry_picker --continue workflow with a merge conflict, then trace how the continuation constructs the eventual PR message. Done means the title and description are preserved or exposed for copying after continuation; the issue does not name a file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100