mapbox / mapbox/github-release-tools
Cherry-pick squashed commit when backporting a squashed PR
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
When a PR is merged via "Rebase and squash", the corresponding backport PR should cherry-pick the squashed commit, instead of individual commits.
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
Start by locating the logic that creates backport pull requests and inspect how it selects commits from a merged pull request. Verify the behavior for a PR merged with “Rebase and squash”; done means the backport cherry-picks the squashed commit rather than individual commits, without changing other merge cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100