Option to preserve manually added labels
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- devops
Research direction
Start by reviewing the labeller.yml label-matching behavior and the sync-labels handling described in the issue. The work is done when an option such as preserve-labels retains manually added labels while the existing default behavior still adds and removes labels based on changed files.
Written by the indexing model from the issue text.
Description
Description:
I would like add an option to:
- Add a label if files are changed, defined in labeller.yml (default behaviour already)
- Don't remove label, if labeller detects that files "belonging to the label" defined in labeller.yml, are changed
sync-labels: does not work in this case.
Could call the option "preserve-labels" or similar.
Description (usecase):
Suppose we have a repo with 2 generations (versions) of a project.
The src code for generations are in 2 different directories.
Some common code is shared.
I define the labeller like so:
labeller.yml:
GENERATION0_LABELLER_LABEL:
- 'common_files/.**'
- 'generation0_files/.**'
GENERATION1_LABELLER_LABEL:
- 'common_files/.**'
- 'generation1_files/.**'
There are cases where, regardless of the files changed, I want to run tests for both generations.
So I apply the label "GENERATION1_LABELLER_LABEL".
The labeller sees that I haven't changed files in "- 'common_files/.' or 'generation1_files/.'.
It removes the label.
Justification:
Currently we require 2 labels to get this to run.
GENERATION0_LABELLER_LABEL
GENERATION1_LABELLER_LABEL
GENERATION0_MANUAL_LABEL
GENERATION1_MANUAL_LABEL
Are you willing to submit a PR?
Not likely, but a possibility if complexity is low
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 488
- PR merge metrics
- No merged PRs in 30d
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/labeler
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
When a workflow is triggered via workflow_dispatch, it cannot match the corresponding branch.Possibly taken @v-chiranjib-swain claimed this 2 days ago. Openbug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
Feature request: top-level `ignore` list for files that should never trigger labelsPossibly taken @janhoy claimed this 104 days ago. Openfeature request
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
solidjs/solid-docs#1716 ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Progress indicated by console logs is off by onePossibly taken @marceliwac claimed this today. Openbug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aws-samples/aws-cdk-examples#1336 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melgarafael/DeskcommCRM#4999 · 1 comment ·
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days