Improve Pull Request + patch series handling
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the current pull-request and patch-series behavior using the netdev example linked in the issue, then trace how the cover letter and patches are represented and grouped. Done means a cover-letter pull request and its patches remain one unit while preserving commit IDs, with CI able to verify the patches against the branch.
Written by the indexing model from the issue text.
Description
Sometimes pull request is used as a cover letter for a patch set. It's done e.g. to allow people to review the code on the mailing list, but if accepted preserve commit ids in case they travel upstream via multiple trees (e.g. drivers spanning subsystems).
Right now patchwork takes the cover letter as a separate PR and the patches are grouped without a cover letter. It'd be good if they remained a single unit. CI could then verify the patches match the code on the branch etc.
Example where the behaviour should be visible:
https://patchwork.ozlabs.org/project/netdev/list/?submitter=1315&state=*
- Dominant language
- Python
- Stars
- 317
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
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.
More from getpatchwork/patchwork
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getpatchwork/patchwork#668 ·
-
bug web-ui
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
getpatchwork/patchwork#546 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
getpatchwork/patchwork#664 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
getpatchwork/patchwork#663 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
getpatchwork/patchwork#645 ·
All issues in getpatchwork/patchwork
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DiamondLightSource/dodal#2211 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openml/openml-python#1749 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sipyourdrink-ltd/bernstein#6191 ·