76a90d082a
Triage is scheduled to run once every 5 minutes but it's often queued up during the day as builders are otherwise occupied with actual CI builds. This can end up in a lot of triage tasks queued up back-to-back. While this doesn't seem to be a huge issue one thing I suspect is that this is perhaps somewhat related to API rate limits getting hit when recent versions were published. In any case there's no need for each and every triage run to do something, it's fine to only have one at a time pending.
38 lines
1.1 KiB
YAML
38 lines
1.1 KiB
YAML
name: "Issue / PR Triage"
|
|
|
|
on:
|
|
issues:
|
|
types: ["labeled"]
|
|
schedule:
|
|
# Run pull request triage every 5 minutes. Ideally, this would be on
|
|
# "labeled" types of pull request events, but that doesn't work if the pull
|
|
# request is from another fork. For example, see
|
|
# https://github.com/actions/labeler/issues/12
|
|
- cron: '*/5 * * * *'
|
|
|
|
concurrency:
|
|
group: issue-triage
|
|
cancel-in-progress: true
|
|
|
|
jobs:
|
|
triage:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
|
|
# Automatically label PRs that touch certain directories with certain
|
|
# labels.
|
|
- uses: bytecodealliance/labeler@schedule-fork
|
|
with:
|
|
repo-token: "${{ secrets.GITHUB_TOKEN }}"
|
|
|
|
# @-mention people who are subscribed to a label when an issue/PR is given
|
|
# that label.
|
|
- uses: bytecodealliance/subscribe-to-label-action@v1
|
|
with:
|
|
repo-token: "${{ secrets.GITHUB_TOKEN }}"
|
|
|
|
# Leave pre-determined comments on issues/PRs that are given a certain label.
|
|
- uses: bytecodealliance/label-messager-action@v1
|
|
with:
|
|
repo-token: "${{ secrets.GITHUB_TOKEN }}"
|