cilium / cilium/github-actions
Feature: Remove triage label from issues based on other labels being added
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
In cilium/cilium, the Issue triage process dictates that triagers should assess reproducibility then apply a label like area/* to complete the triage towards a specific subsystem.
Reviewers and Committers are fairly inconsistent in removing the needs/triage label from the issue when they complete triage, which makes the status of the issue less clear. It'd be nice to auto-enforce consistency on use of this label.
Proposing a feature where MLH would track all updates to issues with a dedicated triage label (default needs/triage), then checks for a list of triage complete labels, and if any of those labels is set, auto-remove the needs/triage label.
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 with the linked Cilium issue triage process and inspect the github-actions repository's MLH logic for issue updates. Trace how the default needs/triage label and area/* labels could be represented and configured. Done means adding a triage-complete label automatically removes needs/triage when that label is applied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100