[PATCH 6/8] SubmittingPatches: clarify GitHub visual
From: Josh Soref via GitGitGadget <hidden>
Date: 2023-12-19 08:42:08
Subsystem:
documentation, the rest · Maintainers:
Jonathan Corbet, Linus Torvalds
From: Josh Soref via GitGitGadget <hidden>
Date: 2023-12-19 08:42:08
Subsystem:
documentation, the rest · Maintainers:
Jonathan Corbet, Linus Torvalds
From: Josh Soref <redacted> Some people would expect a cross to be upright, and potentially have unequal lengths... GitHub uses a white x overlaying a solid red circle to indicate failure. Signed-off-by: Josh Soref <redacted> --- Documentation/SubmittingPatches | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index d7a84f59478..8e19c7f82e4 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches@@ -604,7 +604,7 @@ to your fork of Git on GitHub. You can monitor the test state of all your branches here: `https://github.com/<Your GitHub handle>/git/actions/workflows/main.yml` If a branch did not pass all test cases then it is marked with a red -cross. In that case you can click on the failing job and navigate to ++x+. In that case you can click on the failing job and navigate to "ci/run-build-and-tests.sh" and/or "ci/print-test-failures.sh". You can also download "Artifacts" which are tarred (or zipped) archives with test data relevant for debugging.
--
gitgitgadget