freshlybakedca.ke
Git fork
Merge branch 'js/doc-platform-support-link-fix'
Docfix.
* js/doc-platform-support-link-fix:
docs: fix the `maintain-git` links in `technical/platform-support`
+2
-2
Documentation/technical/platform-support.txt
+2
-2
Documentation/technical/platform-support.txt
···
49
49
notice problems before they are considered "done with review"; whereas
50
50
watching `master` means the stable branch could break for your platform, but
51
51
you have a decent chance of avoiding a tagged release breaking you. See "The
52
-
Policy" in link:../howto/maintain-git.txt["How to maintain Git"] for an
52
+
Policy" in link:../howto/maintain-git.html["How to maintain Git"] for an
53
53
overview of which branches are used in the Git project, and how.
54
54
55
55
* The bug report should include information about what platform you are using.
···
125
125
126
126
To avoid reactive debugging and fixing when changes hit a release or stable, you
127
127
can aim to ensure `next` always works for your platform. (See "The Policy" in
128
-
link:../howto/maintain-git.txt["How to maintain Git"] for an overview of how
128
+
link:../howto/maintain-git.html["How to maintain Git"] for an overview of how
129
129
`next` is used in the Git project.) To do that:
130
130
131
131
* You should add a runner for your platform to the GitHub Actions or GitLab CI