[PATCH] SubmittingPatches: fix Asciidoc syntax in "GitHub CI" section

[PATCH] SubmittingPatches: fix Asciidoc syntax in "GitHub CI" section

[Philippe Blain via GitGitGadget]

From: Philippe Blain <levraiphilippeblain@gmail.com>

A superfluous ']' was added to the title of the GitHub CI section in
f003a91f5c (SubmittingPatches: replace discussion of Travis with GitHub
Actions, 2021-07-22). Remove it.

While at it, format the URL for a GitHub user's workflow runs of Git
between backticks, since if not Asciidoc formats only the first part,
"https://github.com/<Your", as a link, which is not very useful.

Signed-off-by: Philippe Blain <levraiphilippeblain@gmail.com>
---
    SubmittingPatches: fix Asciidoc syntax in "GitHub CI" section

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1077%2Fphil-blain%2Fsubmitting-patches-asciidoc-fix-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1077/phil-blain/submitting-patches-asciidoc-fix-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1077

 Documentation/SubmittingPatches | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index e409022d938..11e03056f2e 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -448,7 +448,7 @@ their trees themselves.
   entitled "What's cooking in git.git" and "What's in git.git" giving
   the status of various proposed changes.
 
-== GitHub CI[[GHCI]]]
+== GitHub CI[[GHCI]]
 
 With an account at GitHub, you can use GitHub CI to test your changes
 on Linux, Mac and Windows. See
@@ -463,7 +463,7 @@ Follow these steps for the initial setup:
 
 After the initial setup, CI will run whenever you push new changes
 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
+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

base-commit: 5a73c6bdc717127c2da99f57bc630c4efd8aed02
-- 
gitgitgadget