sanitizers / sanitizers/patchback-github-app
Allow to remove `backport-` label after successfully creating backport PR, allow to create `backported-` label
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- Python
- Stars
- 14
- Forks
- 10
- Avg merge
- 4m
- Merged PRs (30d)
- 3
Description
It would be helpful to have two (independent) options:
- Remove
backport-<branch_id>label after successfully backporting; - Add
backported-<branch_id>label after successfully backporting (label's name should be configurable similar to the label for creating backports).
This allows to filter PRs to see
- which were backported automatically,
- where backporting failed and manual intervention is needed.
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 tracing the successful backport path and the existing configurable label used to create backports. Check how labels are handled after a backport PR is created, then implement independently configurable removal and addition behavior. Done means successful backports can remove the backport-<branch_id> label, add a configurable backported-<branch_id> label, and preserve filtering for failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100