Different label based on new/changed/removed
Nobody has claimed this yet.
- #79 by @ericcornelissen — closed without merging
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions, typescript, yaml
Research direction
Review the YAML configuration examples in the issue and compare them with the linked ericcornelissen/labeler prototype and its example PRs. Define how added, modified, and removed files should map to labels, including combined and unrestricted patterns; done means pull requests receive the expected labels for each change type.
Written by the indexing model from the issue text.
Description
I was wondering if it is either possible or desired to have a feature to: configure a label based on whether a file was newly created vs. a file was changed (vs. a file was removed).
In configuration I would imagine this could be written as follows:
"label on add":
- on: added
- example/**/*
"label on change":
- on: modified
- example/**/*
"label on remove":
- on: removed
- example/**/*
"label on multiple":
- on:
- added
- modified
- removed
- example/**/*
"or if you don't care":
- example/**/*
"and even": example/**/*
I have a working prototype at ericcornelissen/labeler (example PR added, example PR modified) which I could turn into a Pull Request for this project if there is more interest in this 😄
In practice I want to use this in simple-icons/simple-icons to label Pull Requests with either new icon or icon outdated based on whether a new icon was added or an icon was updated (respectively)
- 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