pytest-dev / pytest-dev/pytest
Review old "needs backport" PRs
Open
Nobody has claimed this yet.
type: infrastructure
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
Looks like we have 35 old PRs with a "needs backport" label:
https://github.com/pytest-dev/pytest/pulls?q=is%3Apr+is%3Aclosed+label%3A%22needs+backport%22
Can we remove that, so we can use the label as a kind of "todo list" in the future still? What about the "backported" label, is that needed really?
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 with the linked search for closed pull requests carrying the "needs backport" label and review the 35 results. Determine which labels are still needed, remove obsolete labels from old PRs, and document the resulting decision about the "needs backport" and "backported" labels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100