This contributes a contribute a prompt benchmarking script; it gets label information for ~100 existing issues - assumed to be correctly labelled - and compares them against the labels predicted by the prompt. This will allow us to benchmark prompt changes to know whether we're improving things or not. Note that there are no prompt improvements in this PR (just some updates for area label changes).
The benchmarking can be re-run via dart tool/bench.dart.
[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.
Contribution guidelines:
- 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.
Breaking changes :heavy_check_mark:
| Package | Change | Current Version | New Version | Needed Version | Looking good? |
| :--- | :--- | ---: | ---: | ---: | ---: |
Changelog Entry :heavy_check_mark:
| Package | Changed Files |
| :--- | :--- |
Changes to files need to be [accounted for](https://github.com/dart-lang/ecosystem/wiki/Changelog) in their respective changelogs.
Coverage :heavy_check_mark:
| File | Coverage |
| :--- | :--- |
This check for [test coverage](https://github.com/dart-lang/ecosystem/wiki/Test-Coverage) is informational (issues shown here will not fail the PR).
API leaks :heavy_check_mark:
The following packages contain symbols visible in the public API, but not exported by the library. Export these symbols or remove them from your publicly visible API.
| Package | Leaked API symbols |
| :--- | :--- |
License Headers :heavy_check_mark:
```
// Copyright (c) 2024, the Dart project authors. Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.
```
| Files |
| :--- |
| _no missing headers_ |
All source files should start with a [license header](https://github.com/dart-lang/ecosystem/wiki/License-Header).
Package publish validation :heavy_check_mark:
| Package | Version | Status |
| :--- | ---: | :--- |
| package:dart_flutter_team_lints | 3.2.0 | already published at pub.dev |
| package:firehose | 0.9.2 | already published at pub.dev |
Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.
github-actions[bot]
commented
2 months ago
This contributes a contribute a prompt benchmarking script; it gets label information for ~100 existing issues - assumed to be correctly labelled - and compares them against the labels predicted by the prompt. This will allow us to benchmark prompt changes to know whether we're improving things or not. Note that there are no prompt improvements in this PR (just some updates for area label changes).
The benchmarking can be re-run via
dart tool/bench.dart.Contribution guidelines:
- 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.