[cherry-picker] [idea 💡] Extend backport sources
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 65
- Forks
- 47
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
I think with https://help.github.com/articles/checking-out-pull-requests-locally/ and https://gist.github.com/piscisaureus/3342247#gistcomment-1566295 cherry-picker could do better and even backport rebase merges and normal merge commits.
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 reading the cherry-picker utility and the linked GitHub pull-request checkout and merge references to understand the current backport flow. Define how rebase merges and normal merge commits should be handled, then verify that both commit forms can be backported successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100