Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Docs: Suggestion to use Labeler #2576
Comments
|
I like it, I think this can be a great help to filter out PRs |
|
Nice! |
|
@brandonroberts @timdeschryver I would add the following things to the .github folder:
labeler.yml # Add 'Project: ngrx.io' label to any ngrx.io file changes
'Project: ngrx.io':
- projets/ngrx.io/*
- projets/ngrx.io/**/*
# Add 'Project: Example App' label to any example-app file changes
'Project: Example App':
- projets/example-app/*
- projets/example-app/**/*
# Add 'Project: Component' label to any change within the 'component' package
'Project: Component':
- modules/component/*
- modules/component/**/*
# Add 'Project: Component Store' label to any change within the 'component-store' package
'Project: Component Store':
- modules/component-store/*
- modules/component-store/**/*
# Add 'Project: Data' label to any change within the 'data' package
'Project: Data':
- modules/data/*
- modules/data/**/*
# Add 'Project: Effects' label to any change within the 'effects' package
'Project: Effects':
- modules/effects/*
- modules/effects/**/*
# Add 'Project: Router Store' label to any change within the 'router-store' package
'Project: Router Store':
- modules/data/*
- modules/data/**/*
# Add 'Project: Schematics' label to any change within the 'schematics' package
'Project: Schematics':
- modules/schematics/*
- modules/schematics/**/*
# Add 'Project: Store' label to any change within the 'store' package
'Project: Store':
- modules/store/*
- modules/store/**/*
# Add 'Project: Store Devtools' label to any change within the 'store-devtools' package
'Project: Store Devtools':
- modules/store-devtools/*
- modules/store-devtools/**/*
# Add 'dependencies' label to any change to npm or yarn related stuff
dependencies:
- package.json
- yarn.locklabel.yml # This workflow will triage pull requests and apply a label based on the
# paths that are modified in the pull request.
#
# The used configurations are set up in .github/labeler.yml
# For more information, see:
# https://github.com/actions/labeler/blob/master/README.md
name: Labeler
on: [pull_request]
jobs:
label:
runs-on: ubuntu-latest
steps:
- uses: actions/labeler@v2
with:
repo-token: "${{ secrets.GITHUB_TOKEN }}" |
|
Seems fine to me @BioPhoton , what do you think @brandonroberts ? There's one typo:
|

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

I thought I open an issue for that as I believe it can save the team a lot of work.
https://github.com/actions/labeler
If this is interesting I would contribute with the workflow file.
Just let me know what you think.
The text was updated successfully, but these errors were encountered: