[triage] contribute an issue triage github workflow
Change-Id: I9b4122bed37b2e4ef3b7c0dcc3c840ebfb2d5fc9 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/370160 Reviewed-by: Lasse Nielsen <lrn@google.com> Commit-Queue: Devon Carew <devoncarew@google.com> Reviewed-by: Nate Bosch <nbosch@google.com>
This commit is contained in:
committed by
Commit Queue
parent
216a14b599
commit
8a65c5056a
@@ -0,0 +1,38 @@
|
|||||||
|
# A workflow to invoke a triage automation bot.
|
||||||
|
#
|
||||||
|
# For more information, see
|
||||||
|
# https://github.com/dart-lang/ecosystem/tree/main/pkgs/sdk_triage_bot and
|
||||||
|
# https://github.com/dart-lang/sdk/blob/main/docs/Triaging-Dart-SDK-issues.md.
|
||||||
|
|
||||||
|
name: Triage Bot
|
||||||
|
|
||||||
|
# Run when an issue is created.
|
||||||
|
on:
|
||||||
|
issues:
|
||||||
|
types:
|
||||||
|
- opened
|
||||||
|
|
||||||
|
# All permissions not specified are set to 'none'.
|
||||||
|
permissions:
|
||||||
|
issues: write
|
||||||
|
|
||||||
|
jobs:
|
||||||
|
triage_issues:
|
||||||
|
runs-on: ubuntu-latest
|
||||||
|
steps:
|
||||||
|
- uses: actions/checkout@a5ac7e51b41094c92402da3b24376905380afc29
|
||||||
|
with:
|
||||||
|
repository: dart-lang/ecosystem
|
||||||
|
|
||||||
|
- uses: dart-lang/setup-dart@f0ead981b4d9a35b37f30d36160575d60931ec30
|
||||||
|
|
||||||
|
- run: dart pub get
|
||||||
|
working-directory: pkgs/sdk_triage_bot
|
||||||
|
|
||||||
|
- name: triage issue
|
||||||
|
working-directory: pkgs/sdk_triage_bot
|
||||||
|
env:
|
||||||
|
ISSUE_URL: ${{ github.event.issue.html_url }}
|
||||||
|
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||||
|
GOOGLE_API_KEY: ${{ secrets.GEMINI_API_KEY }}
|
||||||
|
run: dart bin/triage.dart $ISSUE_URL --dry-run
|
||||||
@@ -1,3 +0,0 @@
|
|||||||
## What are the `@dart-github-bot` comments?
|
|
||||||
|
|
||||||
We're experimenting with triage automation. You may see comments made by a `@dart-github-bot` - that's related to our automation investigations. We may or may not continue experimentation here; for now, you can safely ignore these comments.
|
|
||||||
@@ -44,6 +44,16 @@ on an issue, say so, and consider adding the `needs-info` label to the issue. Is
|
|||||||
with a `needs-info` label are triaged by our [no response] bot; it will auto-close
|
with a `needs-info` label are triaged by our [no response] bot; it will auto-close
|
||||||
the issue after 14 days if the issue reporter does not respond.
|
the issue after 14 days if the issue reporter does not respond.
|
||||||
|
|
||||||
|
## Triage automation
|
||||||
|
|
||||||
|
We're experimenting with triage automation. You may see comments made by a
|
||||||
|
`@dart-github-bot` - that's related to our automation investigations. We may or
|
||||||
|
may not continue experimentation here; for now, you can safely ignore these
|
||||||
|
comments.
|
||||||
|
|
||||||
|
For the source for the triage tool, see
|
||||||
|
https://github.com/dart-lang/ecosystem/tree/main/pkgs/sdk_triage_bot.
|
||||||
|
|
||||||
## Follow up steps for Dart VM and Dart IO Library issues
|
## Follow up steps for Dart VM and Dart IO Library issues
|
||||||
|
|
||||||
Issues filed against the Dart VM (issues with label `area-vm` : [VM issues](https://github.com/dart-lang/sdk/issues?q=is%3Aissue+is%3Aopen+label%3Aarea-vm+)) and IO library (issues with labels `area-core-library` `library-io` : [io library issues](https://github.com/dart-lang/sdk/issues?q=is%3Aissue+is%3Aopen+label%3Aarea-core-library+label%3Alibrary-io)) are triaged at least weekly by a member of the Dart VM team.
|
Issues filed against the Dart VM (issues with label `area-vm` : [VM issues](https://github.com/dart-lang/sdk/issues?q=is%3Aissue+is%3Aopen+label%3Aarea-vm+)) and IO library (issues with labels `area-core-library` `library-io` : [io library issues](https://github.com/dart-lang/sdk/issues?q=is%3Aissue+is%3Aopen+label%3Aarea-core-library+label%3Alibrary-io)) are triaged at least weekly by a member of the Dart VM team.
|
||||||
|
|||||||
Reference in New Issue
Block a user