From 148c1f1344d03edce4a4a222faed9401ad731cac Mon Sep 17 00:00:00 2001
From: cjihrig <cjihrig@gmail.com>
Date: Sun, 31 May 2020 15:39:18 -0400
Subject: [PATCH] meta: wrap flaky test template at 80 characters
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The other issue templates are wrapped at 80 characters. This
commit updates the flaky test template to be consistent.

PR-URL: https://github.com/nodejs/node/pull/33677
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Zeyu Yang <himself65@outlook.com>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
---
 .github/ISSUE_TEMPLATE/4-report-a-flaky-test.md | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/4-report-a-flaky-test.md b/.github/ISSUE_TEMPLATE/4-report-a-flaky-test.md
index b5b005c21bbaae..25ebd736e193c6 100644
--- a/.github/ISSUE_TEMPLATE/4-report-a-flaky-test.md
+++ b/.github/ISSUE_TEMPLATE/4-report-a-flaky-test.md
@@ -8,17 +8,21 @@ labels: "CI / flaky test"
 <!--
 Thank you for reporting a flaky test.
 
-Flaky tests are tests that fail occaisonally in Node.js CI, but not consistently enough to block PRs from landing,
-or that are failing in CI jobs or test modes that are not run for every PR.
+Flaky tests are tests that fail occaisonally in Node.js CI, but not consistently
+enough to block PRs from landing, or that are failing in CI jobs or test modes
+that are not run for every PR.
 
 Please fill in as much of the template below as you're able.
 
 Test: The test that is flaky - e.g. `test-fs-stat-bigint`
 Platform: The platform the test is flaky on - e.g. `macos` or `linux`
-Console Output: A pasted console output from a failed CI job showing the whole failure of the test
+Console Output: A pasted console output from a failed CI job showing the whole
+failure of the test
 Build Links: Links to builds affected by the flaky test
 
-If any investigation has been done, please include any information found, such as how consistently the test fails, whether the failure could be reproduced locally, when the test started failing, or anything else you think is relevant.
+If any investigation has been done, please include any information found, such
+as how consistently the test fails, whether the failure could be reproduced
+locally, when the test started failing, or anything else you think is relevant.
 -->
 
 * **Test**: