Feature request: top-level `ignore` list for files that should never trigger labels
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- github-actions, typescript
- Domain
- devops
Research direction
Start by tracing how the action builds its changed-files set, loads the top-level configuration, and evaluates per-rule globs and negations. Add a top-level ignore list whose matching files are removed before any label rule runs, then verify that lock-file-only changes no longer trigger directory-based labels while unrelated files still do.
Written by the indexing model from the issue text.
Description
Description
Add a top-level ignore key (a list of globs) whose matches are removed from the changed-files set before any label rule is evaluated, so those files can never, on their own, cause a label to be applied.
This is different from the existing per-rule ! negation: negation has to be repeated inside every rule and is evaluated per-rule, so it can't express "these files should never matter to any label" in a single place.
Justification
Lock files are the motivating case. A dependency bump can rewrite many lock files (gradle.lockfile, package-lock.json, poetry.lock, ...) scattered across per-module directories, without touching any real source. With directory-based rules like:
module-foo:
- changed-files:
- any-glob-to-any-file:
- modules/foo/**
every module whose lock file changed gets labeled as if its source were modified. Excluding lock files inside each rule is verbose and easy to forget whenever a new rule is added. A single top-level ignore list would solve it once:
ignore:
- '**/*.lock'
- '**/gradle.lockfile'
Are you willing to submit a PR?
Possibly, if the approach is agreed.
- 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
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Label PR on titleOpenfeature request
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
db-ux-design-system/core-web#8856 ·
Maintainers usually reply within 1 day
-
'!' breaking change is lost when the commit also has an empty BREAKING CHANGE footerPossibly taken @wittdennis claimed this today. Openpriority: p3 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
googleapis/release-please#2971 ·
Maintainers usually reply within 1 day
-
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