commit 4ba6f15e2849ebd19419695d0ae931b4c38498ae
author Devon Carew <devoncarew@google.com> Wed Sep 04 14:21:59 2024 -0700
committer GitHub <noreply@github.com> Wed Sep 04 14:21:59 2024 -0700
tree 2304d39331d08217936109cec11c6aa0c0c7e302
parent 3496f5485395d93d4a9fbcc87464d48ea61a9395

update the prompt to include `needs-info` (#296)

- update the prompt to include triaging issues w/ `needs-info` labels
- `[breaking change]` issues should have `breaking-change-request`
labels but don't necessarily need area labels
- add 5 'few-shot' examples in the classification prompt
- update benchmark expectations
- classification performance has generally improved from 56% to 65%

---

- [x] I’ve reviewed the contributor guide and applied the relevant
portions to this PR.

<details>
  <summary>Contribution guidelines:</summary><br>

- See our [contributor
guide](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md)
for general expectations for PRs.
- Larger or significant changes should be discussed in an issue before
creating a PR.
- Contributions to our repos should follow the [Dart style
guide](https://dart.dev/guides/language/effective-dart) and use `dart
format`.
- Most changes should add an entry to the changelog and may need to [rev
the pubspec package
version](https://github.com/dart-lang/sdk/blob/main/docs/External-Package-Maintenance.md#making-a-change).
- Changes to packages require [corresponding
tests](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md#Testing).

Note that many Dart repos have a weekly cadence for reviewing PRs -
please allow for some latency before initial review feedback.
</details>