summaryrefslogtreecommitdiffstats
path: root/SubmittingPatches.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2021-11-22 08:53:52 -0800
committerJunio C Hamano <gitster@pobox.com>2021-11-22 08:53:52 -0800
commit76545588739a2c62fbdddea72038d2d10e2afad2 (patch)
tree31a70a73998086394057e74b5b2b7155e25a3316 /SubmittingPatches.txt
parentf5008a039d585310d71e52b5d9f888dab4924eeb (diff)
downloadgit-htmldocs-76545588739a2c62fbdddea72038d2d10e2afad2.tar.gz
Autogenerated HTML docs for v2.34.0-7-g0ea90
Diffstat (limited to 'SubmittingPatches.txt')
-rw-r--r--SubmittingPatches.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/SubmittingPatches.txt b/SubmittingPatches.txt
index e409022d9..11e03056f 100644
--- a/SubmittingPatches.txt
+++ b/SubmittingPatches.txt
@@ -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