{"thread":{"id":"56890","subject":"[PATCH] SubmittingPatches: fix Asciidoc syntax in \"GitHub CI\" section","startedAt":"2021-11-13T20:38:11Z","lastAt":"2021-11-13T20:38:11Z","messageCount":1,"participants":["Philippe Blain via GitGitGadget"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"441073","messageId":"pull.1077.git.1636835885198.gitgitgadget@gmail.com","threadId":"56890","inReplyTo":null,"subject":"[PATCH] SubmittingPatches: fix Asciidoc syntax in \"GitHub CI\" section","fromName":"Philippe Blain via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2021-11-13T20:38:05Z","receivedAt":"2021-11-13T20:38:11Z","isPatch":true,"sender":{"key":"levraiphilippeblain@gmail.com","avatar":"https://avatars.githubusercontent.com/u/44212482?v=4"},"body":"From: Philippe Blain <levraiphilippeblain@gmail.com>\n\nA superfluous ']' was added to the title of the GitHub CI section in\nf003a91f5c (SubmittingPatches: replace discussion of Travis with GitHub\nActions, 2021-07-22). Remove it.\n\nWhile at it, format the URL for a GitHub user's workflow runs of Git\nbetween backticks, since if not Asciidoc formats only the first part,\n\"https://github.com/<Your\", as a link, which is not very useful.\n\nSigned-off-by: Philippe Blain <levraiphilippeblain@gmail.com>\n---\n    SubmittingPatches: fix Asciidoc syntax in \"GitHub CI\" section\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-1077%2Fphil-blain%2Fsubmitting-patches-asciidoc-fix-v1\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1077/phil-blain/submitting-patches-asciidoc-fix-v1\nPull-Request: https://github.com/gitgitgadget/git/pull/1077\n\n Documentation/SubmittingPatches | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\nindex e409022d938..11e03056f2e 100644\n--- a/Documentation/SubmittingPatches\n+++ b/Documentation/SubmittingPatches\n@@ -448,7 +448,7 @@ their trees themselves.\n   entitled \"What's cooking in git.git\" and \"What's in git.git\" giving\n   the status of various proposed changes.\n \n-== GitHub CI[[GHCI]]]\n+== GitHub CI[[GHCI]]\n \n With an account at GitHub, you can use GitHub CI to test your changes\n on Linux, Mac and Windows. See\n@@ -463,7 +463,7 @@ Follow these steps for the initial setup:\n \n After the initial setup, CI will run whenever you push new changes\n to your fork of Git on GitHub.  You can monitor the test state of all your\n-branches here: https://github.com/<Your GitHub handle>/git/actions/workflows/main.yml\n+branches here: `https://github.com/<Your GitHub handle>/git/actions/workflows/main.yml`\n \n If a branch did not pass all test cases then it is marked with a red\n cross. In that case you can click on the failing job and navigate to\n\nbase-commit: 5a73c6bdc717127c2da99f57bc630c4efd8aed02\n-- \ngitgitgadget\n"}]}