Rename ecosystem testing package to canary

.github/ISSUE_TEMPLATE/canary.md

@@ -0,0 +1,5 @@
+---
+name: "package:canary"
+about: "Create a bug or file a feature request against package:canary."
+labels: "package:canary"
+---

.github/test_repos/repos.json

@@ -1,5 +1,5 @@
 {
-    "$schema": "../../pkgs/quest/schema.json",
+    "$schema": "../../pkgs/canary/schema.json",
     "https://github.com/mosuem/my_app_old_web": {
         "level": "analyze"
     },

.github/workflows/ecosystem_test.yaml → .github/workflows/canary.yaml

@@ -1,4 +1,4 @@
-name: Ecosystem test
+name: Canary
 
 on:
   workflow_call:

.github/workflows/ecosystem_test_internal.yaml → .github/workflows/canary_internal.yaml

@@ -1,4 +1,4 @@
-name: Ecosystem test:Internal
+name: Canary:Internal
 
 on:
   pull_request:
@@ -7,7 +7,7 @@ on:
 
 jobs:
   test_ecosystem:
-    uses: ./.github/workflows/ecosystem_test.yaml
+    uses: ./.github/workflows/canary.yaml
     with:
       repos_file: .github/test_repos/repos.json
       local_debug: true

.github/workflows/quest.yml → .github/workflows/canary_test.yml

@@ -1,24 +1,24 @@
-name: package:quest
+name: package:canary
 
 permissions: read-all
 
 on:
   pull_request:
     branches: [ main ]
     paths:
-      - '.github/workflows/quest.yml'
-      - 'pkgs/quest/**'
+      - '.github/workflows/canary.yml'
+      - 'pkgs/canary/**'
   push:
     branches: [ main ]
     paths:
-      - '.github/workflows/quest.yml'
-      - 'pkgs/quest/**'
+      - '.github/workflows/canary.yml'
+      - 'pkgs/canary/**'
   schedule:
     - cron: '0 0 * * 0' # weekly
 
 defaults:
   run:
-    working-directory: pkgs/quest
+    working-directory: pkgs/canary
 
 env:
   GH_TOKEN: ${{ github.token }}

.github/workflows/post_summaries.yaml

@@ -8,7 +8,7 @@ on:
     workflows:
       - Publish:Internal
       - Health:Internal
-      - Ecosystem test:Internal
+      - Canary:Internal
     types:
       - completed
 

README.md

@@ -9,6 +9,7 @@ This repository is home to general Dart Ecosystem tools and packages.
 | Package | Description | Version |
 | --- | --- | --- |
 | [blast_repo](pkgs/blast_repo/) | A tool to bulk validate and fix GitHub repos. |  |
+| [canary](pkgs/canary/) | Test package upgrades against the ecosystem. |  |
 | [corpus](pkgs/corpus/) | A tool to calculate the API usage for a package. |  |
 | [dart_flutter_team_lints](pkgs/dart_flutter_team_lints/) | An analysis rule set used by the Dart and Flutter teams. | [![pub package](https://img.shields.io/pub/v/dart_flutter_team_lints.svg)](https://pub.dev/packages/dart_flutter_team_lints) |
 | [firehose](pkgs/firehose/) | A tool to automate publishing of Pub packages from GitHub actions. | [![pub package](https://img.shields.io/pub/v/firehose.svg)](https://pub.dev/packages/firehose) |

pkgs/quest/README.md → pkgs/canary/README.md

@@ -1,5 +1,5 @@
-# Quest: Ecosystem Testing for Dart Packages
-Embark your package on a quest of testing against a suite of applications. This helps identify potential breaking changes introduced by package updates, ensuring seamless integration across the ecosystem.
+# Canary: Ecosystem Testing for Dart Packages
+Before publishing, send a canary out to test a package against a suite of applications. This helps identify potential breaking changes introduced by package updates, ensuring seamless integration across the ecosystem.
 
 ## What does it do?
 It checks if your package upgrade would result in failures in the ecosystem. This is achieved by running the following pseudocode:
@@ -35,9 +35,9 @@ for (final app in applicationSuite) {
 }
 ```
 
-2. Add a workflow file with the following contents:
+2. Add a workflow file `canary.yaml` with the following contents:
 ```yaml
-name: Ecosystem test
+name: Canary
 
 on:
   pull_request:
@@ -46,12 +46,12 @@ on:
 
 jobs:
   test_ecosystem:
-    uses: dart-lang/ecosystem/.github/workflows/ecosystem_test.yaml@main
+    uses: dart-lang/ecosystem/.github/workflows/canary.yaml@main
     with:
       repos_file: .github/test_repos/repos.json
 ```
 
-3. To show the markdown result as a comment, also add a workflow file
+3. To show the markdown result as a comment, also add a workflow file `post_summaries.yaml`
 ```yaml
 name: Comment on the pull request
 
@@ -60,9 +60,7 @@ on:
   # do things like create comments on the PR, even if the original workflow couldn't.
   workflow_run:
     workflows: 
-      - Health
-      - Publish
-      - Ecosystem test
+      - Canary
     types:
       - completed