Support using other labels as criteria
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 492
- PR merge metrics
- No merged PRs in 30d
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"
Contributor 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.
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.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100