add seperated labels-to-remove-when-unstale for issues and PRs
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
Research direction
Start by locating the configuration and label-removal handling for the existing labels-to-remove-when-unstale option, then inspect any tests covering issue and pull-request behavior. Done means the configuration can specify different labels to remove for issues and pull requests, with tests confirming both cases.
Written by the indexing model from the issue text.
Description
I have use case where I want to remove different kind of labels from issues and PRs please allow to separate between them
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 438
- Avg merge
- 27d 8h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 actions/stale
-
Stale label remains after pushing a new commitPossibly taken @v-chiranjib-swain claimed this 21 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Closing items while paginating can skip open pull requestsPossibly taken @v-chiranjib-swain claimed this 93 days ago. Openbug
-
Ignore issues which has linked open PRsPossibly taken A pull request linked to this issue is open or already merged. Openfeature request
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
db-ux-design-system/core-web#8856 ·
Maintainers usually reply within 1 day
-
'!' breaking change is lost when the commit also has an empty BREAKING CHANGE footerPossibly taken @wittdennis claimed this today. Openpriority: p3 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
googleapis/release-please#2971 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
🛠️ dette technique
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
betagouv/mon-entreprise#4752 · 1 comment ·
Maintainers usually reply within 5 days