Support using other labels as criteria
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- ci-cd
Research direction
Start by tracing the existing file-path criteria and the YAML configuration shown in the issue. Determine how pull-request labels can participate in the same criteria, then verify that a rule combining !VERSION with !label:skip-release produces no additional labels when skip-release is present.
Written by the indexing model from the issue text.
Description
This action so far has been based on using the file path(s) to determine which labels to set, but would it be possible to also have it support labels that are already on the PR? My use case is that I want to add a label if the VERSION file has not been modified. However if the PR has the label skip-release, that file is no longer required to be modified, thus no additional labels should be produced.
One potential way for this to work would be something like this:
needs-version-bump:
- all:
- "!VERSION"
- "!label:skip-release"
- 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 103 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 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
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
franciscoBSalgueiro/en-croissant#1111 ·
Maintainers usually reply within 2 days
-
area/providers type/feature version/v2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anomalyco/opencode#64845 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day