misc: Add labeler workflow to automatically label PRs based on files changed#3151
misc: Add labeler workflow to automatically label PRs based on files changed#3151erin-le wants to merge 2 commits into
Conversation
This automatically labels pull requests based on some simple file path rules.
There was a problem hiding this comment.
Pull request overview
Adds a GitHub Actions workflow to automatically apply repository labels to pull requests based on the paths of changed files, using a central .github/labeler.yml ruleset. This helps keep labeling consistent and reduces manual triage overhead.
Changes:
- Added a new
Pull Request Labelerworkflow usingactions/labeler. - Introduced
.github/labeler.ymlwith path-based label rules for major gem5 subsystems.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .github/workflows/label.yaml | Adds the GitHub Actions workflow which runs the labeler on PRs. |
| .github/labeler.yml | Defines the path/glob rules mapping changed files to labels. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - all-globs-to-any-file: [src/sim/**, '!src/sim/se_workload.**', '!src/sim/syscall**.**', '!src/sim/process.**'] | ||
|
|
||
| sim-se: | ||
| - changed-files: | ||
| - any-glob-to-any-file: ['**/se_**.**', '**/syscall**.**', '**/se_binary_workload.py', src/sim/process.**, src/sim/fd_**.**] |
There was a problem hiding this comment.
@BobbyRBruce: Do you know if process_impl.hh falls under sim-se? I skimmed through the commit messages in process_impl.hh and none of the ones I saw mentioned SE mode specifically. Many of the commit messages were quite old, however, so that may play a role in SE mode not being mentioned.
This commit extends the labeler action to include all relevant labels and corresponding path globs.
This PR adds a workflow to automatically assign labels to PRs based on the files changed. The path rules in
labeler.ymlwere written based on how labels have typically been assigned in the gem5 repository in the past. The discussion for this workflow can be seen in #3095, and the work for this workflow was started by @lhartung.