From b65c0db244487d0e91646cdbe38e6e2a7f7dd921 Mon Sep 17 00:00:00 2001 From: Chinmay Garde Date: Sun, 27 Jun 2021 15:55:18 -0700 Subject: [PATCH] Remove presubmit flake reporting instructions from issue template. The effectiveness of this step was reviewed during the staff meeting. We are already filing issues for flakes as we find them and this form is not used very often. It was decided to avoid instructing users to report flakes this way and forego reviewing the responses during triage runs each week. --- .github/PULL_REQUEST_TEMPLATE.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index d4ee0dd02a5d8..26f5225b9fa53 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -15,7 +15,6 @@ writing and running engine tests. - [ ] I updated/added relevant documentation (doc comments with `///`). - [ ] I signed the [CLA]. - [ ] All existing and new tests are passing. -- [ ] The reviewer has submitted any presubmit flakes in this PR using the [engine presubmit flakes form] before re-triggering the failure. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. @@ -29,4 +28,3 @@ If you need help, consider asking for advice on the #hackers-new channel on [Dis [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/wiki/Chat -[engine presubmit flakes form]: https://forms.gle/Wc1VyFRYJjQTH6w5A