labeler.yml example to match all repo files
See original GitHub issueI’m trying to set up a rule to apply a needs triage
label for any file change in a repo, but I can’t get it to work without manually specifying at least one folder in the path.
Here are some combinations I’ve tried without success:
needs triage:
- '*'
needs triage:
- '*'
- '**/*'
needs triage:
- ./*
- ./**/*
needs triage:
- '*'
It works for changes in a single folder if I provide at least part of a path, e.g.:
needs triage:
- .github/*
Any help would be awesome!
Issue Analytics
- State:
- Created 4 years ago
- Reactions:8
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Adding Labels Automatically Using GitHub Actions - Diana Lau
While exploring what GitHub Actions can do, I find the Labeler action very useful for this purpose. ... Make sure you have labeler.yml...
Read more >Github action for auto labeler - Stack Overflow
all : match ALL globs against ALL changed paths. Example .github/workflows/labeler.yml. name: Labeler on: [pull_request] ...
Read more >jimschubert/labeler-action - Docker Image
This action requires a configuration file defined at .github/labeler.yml in your repository. The contents must follow either the simple schema or the full ......
Read more >Add useful labels to your Pull Requests with Github Actions
yml file you can configure the action to assign labels per module or part of the app: You can find the syntax of...
Read more >Labels - GitLab Docs
You can assign labels to any issue, merge request, or epic. ... On the top bar, select Main menu > Projects and find...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This worked for me:
the
./
at the start doesn’t do anything for me, it doesn’t workHello everyone! Thank you @Robvdhout for the provided solution! The confusing syntax (
./
) has been removed from the README. I’m closing the issue. Please contact us if you have any concerns.