- Apr 11, 2024
-
-
anarcat authored
-
- Apr 04, 2024
-
-
anarcat authored
-
- Mar 27, 2024
-
-
anarcat authored
-
- Mar 20, 2024
- Jan 10, 2024
-
-
anarcat authored
-
- Oct 03, 2023
-
-
anarcat authored
-
- Sep 28, 2023
- Aug 08, 2023
-
-
anarcat authored
back in 9d9aed39 (use <a id=""> instead of name, as name is not HTML5, 2023-06-01) we switched everything to id= but overlooked that id= actually gets redacted by GitLab's sanitizer. With this, we should be able to get the anchors through the filter even if it generates non-conformant HTML5.
-
- Jun 26, 2023
- Jun 08, 2023
-
-
anarcat authored
-
- Jun 01, 2023
- May 30, 2023
- May 29, 2023
-
-
anarcat authored
See: team#41180
-
- May 25, 2023
-
-
anarcat authored
-
- May 24, 2023
- May 18, 2023
- May 04, 2023
-
-
anarcat authored
-
- Nov 10, 2022
-
-
anarcat authored
-
- Mar 16, 2022
-
-
anarcat authored
-
- Nov 08, 2021
-
-
anarcat authored
-
- Nov 04, 2021
-
-
anarcat authored
-
anarcat authored
-
anarcat authored
The rationale is that (eventually? hopefully?) that documentation will be irrelevant as all repos will have been migrated. In general, we put migration docs in the *source* service, not the target, because of that reason. We keep the heading and a link to avoid breaking links.
-
anarcat authored
-
- Oct 02, 2021
-
-
anarcat authored
-
- Sep 28, 2021
-
-
anarcat authored
-
- May 06, 2021