Update

.cirrus.yml

@@ -1,34 +1,28 @@
 # CIRRUS CONFIGURATION FILE
 # https://cirrus-ci.org/guide/writing-tasks/
 
-# YAML anchors used to share fields between tasks.
-# See https://confluence.atlassian.com/bitbucket/yaml-anchors-960154027.html
-
-
-use_compute_credits: $CIRRUS_USER_COLLABORATOR == 'true'
-
 environment:
   # For details about environment variables used in Cirrus, including how encrypted variables work,
   # see https://cirrus-ci.org/guide/writing-tasks/#environment-variables
-  GCLOUD_SERVICE_ACCOUNT_KEY: ENCRYPTED[f12abe60f5045d619ef4c79b83dd1e0722a0b0b13dbea95fbe334e2db7fffbcd841a5a92da8824848b539a19afe0c9fb]
   # We change Flutter's directory to include a space in its name (see $CIRRUS_WORKING_DIR) so that
   # we constantly test path names with spaces in them. The FLUTTER_SDK_PATH_WITH_SPACE variable must
   # therefore have a space in it.
   FLUTTER_SDK_PATH_WITH_SPACE: "flutter sdk"
   # We force BOT to true so that all our tools know we're in a CI environment. This avoids any
   # dependency on precisely how Cirrus is detected by our tools.
   BOT: "true"
-  # Unsetting CIRRUS_CHANGE_MESSAGE and CIRRUS_COMMIT_MESSAGE as they might include non-ASCII
-  # characters which makes Gradle crash. See: https://github.com/flutter/flutter/issues/24935
-  # TODO(amirha): remove once we've migrated to newer Gradle
-  CIRRUS_CHANGE_MESSAGE: ""
-  CIRRUS_COMMIT_MESSAGE: ""
+
+gcp_credentials: ENCRYPTED[!ebad0a1f4f7a446b77944c33651460a7ab010b4617273cb016cf354eb8fc22aa92e37a3c58bfa4a0c40a799351e027a6!]
 
 # LINUX SHARDS
 task:
-  container:
-    # https://cirrus-ci.org/guide/docker-builder-vm/#dockerfile-as-a-ci-environment
+  gke_container:
     dockerfile: "dev/ci/docker_linux/Dockerfile"
+    builder_image_name: docker-builder-linux # gce vm image
+    builder_image_project: flutter-cirrus
+    cluster_name: test-cluster
+    zone: us-central1-a
+    namespace: default
     cpu: $CPU
     memory: $MEMORY
     use_in_memory_disk: $USE_IN_MEMORY_DISK
@@ -121,10 +115,10 @@ task:
         MEMORY: 10G
         SHOULD_UPDATE_PACKAGES: "FALSE"
       script:
-        - (cd packages/flutter_tools; pub get)
-        - (cd packages/flutter_tools/test/data/asset_test/main; pub get)
-        - (cd packages/flutter_tools/test/data/asset_test/font; pub get)
-        - (cd dev/bots; pub get)
+        - (cd packages/flutter_tools; dart __deprecated_pub get)
+        - (cd packages/flutter_tools/test/data/asset_test/main; dart __deprecated_pub get)
+        - (cd packages/flutter_tools/test/data/asset_test/font; dart __deprecated_pub get)
+        - (cd dev/bots; dart __deprecated_pub get)
         - dart --enable-asserts ./dev/bots/test.dart
 
     - name: tool_tests-commands-linux
@@ -137,57 +131,28 @@ task:
         MEMORY: 10G
         SHOULD_UPDATE_PACKAGES: "FALSE"
       script:
-        - (cd packages/flutter_tools; pub get)
-        - (cd dev/bots; pub get)
-        - dart --enable-asserts ./dev/bots/test.dart
-
-    - name: web_integration_tests
-      only_if: "changesInclude('.cirrus.yml', 'dev/**', 'packages/flutter/**', 'packages/flutter_test/**', 'packages/flutter_tools/**', 'packages/flutter_web_plugins/**', 'bin/**') && $CIRRUS_PR != ''"
-      environment:
-        # As of October 2019, the Web shards needed more than 6G of RAM.
-        CPU: 2
-        MEMORY: 8G
-        CHROME_NO_SANDBOX: true
-      script:
+        - (cd packages/flutter_tools; dart __deprecated_pub get)
+        - (cd dev/bots; dart __deprecated_pub get)
         - dart --enable-asserts ./dev/bots/test.dart
 
     - name: docs-linux # linux-only
-      # TODO(fujino): Make this pre-submit only once we have migrated docs generation to LUCI (https://github.com/flutter/flutter/issues/64212).
       environment:
-        # TODO(tvolkert): optimize CPU and MEMORY settings once docs generation is more efficient (https://github.com/flutter/flutter/issues/60646).
         CPU: 4
-        MEMORY: 8G
-        # For uploading master docs to Firebase master branch staging site
-        FIREBASE_MASTER_TOKEN: ENCRYPTED[eb768d18798fdc5abfe09b224e1724c4d82831d715ccf90df2c79d618c317216cbd99493278361f6fe7948b409b603f0]
-        # For uploading stable docs to Firebase public live site
-        FIREBASE_PUBLIC_TOKEN: ENCRYPTED[37e8b82f167864cae9a3f4d2cf3f37dea331d9375c295327c45de524f6c588fa6f6d63e5784f10f6d43ce29689f36c92]
+        MEMORY: 12G
+      only_if: "$CIRRUS_PR != ''"
       script:
         - ./dev/bots/docs.sh
 
     - name: customer_testing-linux
       only_if: "$CIRRUS_PR != ''"
-      # environment:
+      environment:
         # Empirically, this shard runs fine at 1 CPU and 4G RAM as of October 2019. We will probably
         # want to grow this container when we invite people to add their tests in large numbers.
+        SHOULD_UPDATE_PACKAGES: "FALSE"
       script:
-        - rm -rf bin/cache/pkg/tests
-        - git clone https://github.com/flutter/tests.git bin/cache/pkg/tests
-        - dart --enable-asserts dev/customer_testing/run_tests.dart --skip-on-fetch-failure --skip-template bin/cache/pkg/tests/registry/*.test
-
-    - name: web_smoke_test
-      only_if: "changesInclude('.cirrus.yml', 'examples/hello_world/**' ,'dev/**', 'packages/flutter/**', 'packages/flutter_test/**', 'packages/flutter_tools/lib/src/test/**', 'packages/flutter_web_plugins/**', 'bin/**') && $CIRRUS_PR != ''"
-      environment:
-        # Tests Hello World with Flutter Web Engine using Flutter Driver. Should not need more resources.
-        CPU: 2
-        MEMORY: 2G
-        CHROME_NO_SANDBOX: true
-      script:
-        - flutter config --enable-web
-        - git clone https://github.com/flutter/web_installers.git
-        - cd web_installers/packages/web_drivers/
-        - pub get
-        - dart lib/web_driver_installer.dart chromedriver --install-only
-        - chromedriver/chromedriver --port=4444 &
-        - sleep 1
-        - cd ../../../examples/hello_world/
-        - flutter drive --target=test_driver/smoke_web_engine.dart -d web-server --profile --browser-name=chrome
+        # Cirrus doesn't give us the master branch, so we have to fetch it for ourselves,
+        # otherwise we won't be able to figure out how old or new our current branch is.
+        - git config user.email "cirrus-bot@invalid"
+        - git fetch origin master:master
+        # The actual logic is in a shell script so that it can be shared between CIs.
+        - (cd dev/customer_testing/; ./ci.sh)

.github/ISSUE_TEMPLATE/1_activation.md

@@ -32,6 +32,9 @@ assignees: ''
 
 ## Logs
 
+<details>
+<summary>Logs</summary>
+
 <!--
       Include the full logs of the commands you are running between the lines
       with the backticks below. If you are running any "flutter" commands,
@@ -46,3 +49,5 @@ assignees: ''
 
 ```
 ```
+
+</details>

.github/ISSUE_TEMPLATE/2_bug.md

@@ -23,24 +23,46 @@ assignees: ''
 
 ## Steps to Reproduce
 
-<!-- You must include full steps to reproduce so that we can reproduce the problem. -->
+<!-- Please include full steps to reproduce so that we can reproduce the problem. -->
 
-1. Run `flutter create bug`.
-2. Update the files as follows: ... <!-- include every file that is different from the template app! -->
-3. ... <!-- describe how to reproduce the problem -->
+1. Execute `flutter run` on the code sample <!-- (see "Code sample" section below) -->
+2. ... <!-- describe steps to demonstrate bug -->
+3. ... <!-- for example "Tap on X and see a crash" -->
 
 **Expected results:** <!-- what did you want to see? -->
 
 **Actual results:** <!-- what did you see? -->
 
+<details>
+<summary>Code sample</summary>
+
+<!--
+      Please create a minimal reproducible sample that shows the problem
+      and attach it below between the lines with the backticks.
+
+      To create it you can use `flutter create bug` command and update the `main.dart` file.
+
+      Alternatively, you can use https://dartpad.dev/
+      which is capable of creating and running small Flutter apps.
+
+      Without this we will unlikely be able to progress on the issue, and because of that
+      we regretfully will have to close it.
+-->
+
+```dart
+```
+
+</details>
+
 <details>
   <summary>Logs</summary>
 
 <!--
       Run your application with `flutter run --verbose` and attach all the
       log output below between the lines with the backticks. If there is an
       exception, please see if the error message includes enough information
-      to explain how to solve the issue.
+      to explain how to solve the issue. If there is a crash, please include
+      the entirety of the crash log including the backtrace.
 -->
 
 ```
@@ -60,3 +82,12 @@ assignees: ''
 ```
 
 </details>
+
+
+<!--
+      Consider also attaching screenshots and/or videos to better
+      illustrate the issue.
+
+      You can upload them directly on GitHub.
+      Beware that video file size is limited to 10MB.
+-->

.github/ISSUE_TEMPLATE/3_feature_request.md

@@ -38,7 +38,10 @@ assignees: ''
 <!--
      Briefly but precisely describe what you would like Flutter to be able to do.
 
-     Consider attaching images showing what you are imagining.
+     Consider attaching something showing what you are imagining:
+      * images
+      * videos
+      * code samples
 
      Does this have to be provided by Flutter directly, or can it be provided
      by a package on pub.dev/flutter? If so, maybe consider implementing and

.github/ISSUE_TEMPLATE/4_performance_others.md

@@ -48,6 +48,9 @@ assignees: ''
 
 ## Logs
 
+<details>
+<summary>Logs</summary>
+
 <!--
      Run `flutter analyze` and attach any output of that command below.
      If there are any analysis errors, try resolving them before filing this issue.
@@ -60,3 +63,5 @@ assignees: ''
 
 ```
 ```
+
+</details>

.github/ISSUE_TEMPLATE/5_performance_speed.md

@@ -32,7 +32,6 @@ assignees: ''
      using profile mode with Skia tracing enabled, as follows:
        flutter channel master
        flutter run --profile --trace-skia
-     Then press ‘P’ to enable the performance overlay.
 
      The bleeding edge master channel is encouraged here because Flutter is
      constantly fixing bugs and improving its performance. Your problem in an
@@ -46,6 +45,9 @@ assignees: ''
      so we know which functions might be causing it. See "How to Collect
      and Read Timeline Traces" on this blog post:
        https://medium.com/flutter/profiling-flutter-applications-using-the-timeline-a1a434964af3#a499
+     Make sure the performance overlay is turned OFF when recording the
+     trace as that may affect the performance of the profile run.
+     (Pressing ‘P’ on the command line toggles the overlay.)
 -->
 
 <!--
@@ -60,6 +62,9 @@ assignees: ''
 
 ## Logs
 
+<details>
+<summary>Logs</summary>
+
 <!--
      Run `flutter analyze` and attach any output of that command below.
      If there are any analysis errors, try resolving them before filing this issue.
@@ -72,3 +77,5 @@ assignees: ''
 
 ```
 ```
+
+</details>

.github/ISSUE_TEMPLATE/6_infrastructure.md

@@ -1,5 +1,5 @@
 ---
-name: I want to file a bug or feature request about Flutter's CI infrastructure
+name: The CI infrastructure used by Flutter has a problem
 about: As a contributor, you want to file an issue about the build/test/release
   infra, e.g. dashboards (http://flutter-dashboard.appspot.com), devicelab,
   LUCI (https://ci.chromium.org/p/flutter) etc.

.github/ISSUE_TEMPLATE/7_cherry_pick.yml

@@ -0,0 +1,85 @@
+name: Request a cherry-pick.
+description: As a contributor, you would like to request that a feature be cherry-picked into a release.
+title: '[CP] <title>'
+labels: ['cp: review']
+body:
+  - type: input
+    id: issue_link
+    attributes:
+      label: issue_link
+      description: What is the link to the issue this cherry-pick is addressing?
+    validations:
+      required: true
+  - type: input
+    id: commit_hash
+    attributes:
+      label: Commit Hash
+      description: What is the shortened commit hash that has been merged to master/main?
+    validations:
+      required: true
+  - type: dropdown
+    id: Target
+    attributes:
+      label: Target
+      description: Should this be cherry-picked to beta or stable?
+      options:
+        - stable
+        - beta
+    validations:
+      required: true
+  - type: input
+    id: pr_link
+    attributes:
+      label: pr_link
+      description: >-
+        Link to an open PR that cherrypick's this into the target release branch.
+        The current branches can be found under release-caniddate-branch.version for [beta](https://github.com/flutter/flutter/blob/beta/bin/internal/release-candidate-branch.version) and [stable](https://github.com/flutter/flutter/blob/stable/bin/internal/release-candidate-branch.version)
+    validations:
+      required: true
+  - type: input
+    id: impacted_users
+    attributes:
+      label: Impacted Users
+      description: Approximately who will hit this issue (ex. all Flutter devs, Windows developers, all end-customers, apps using X framework feature)?
+    validations:
+      required: true
+  - type: textarea
+    id: impact_description
+    attributes:
+      label: Impact Description
+      description: What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)? Does it impact development (ex. flutter doctor crashes when Android Studio is installed), or the shipping production app (the app crashes on launch)
+    validations:
+      required: true
+  - type: textarea
+    id: workaround
+    attributes:
+      label: Workaround
+      description: Is there a workaround for this issue?
+    validations:
+      required: true
+  - type: dropdown
+    id: risk
+    attributes:
+      label: Risk
+      description: What is the risk level of this cherry-pick?
+      options:
+        - low
+        - medium
+        - high
+    validations:
+      required: true
+  - type: dropdown
+    id: test_coverage
+    attributes:
+      label: Test Coverage
+      description: Are you confident that your fix is well-tested by automated tests?
+      options:
+        - "yes"
+        - "no"
+    validations:
+      required: true
+  - type: textarea
+    id: fix_steps
+    attributes:
+      label: Validation Steps
+      description: What are the steps to validate that this fix works?