Skip to content

Fix most bare URLs in project

Evan Read requested to merge docs/fix-bare-urls-in-projects into master

What does this MR do?

Bare Markdown URLs aren't automatically converted to clickable links in HTML.

This MR resolves most instances of that in the project.

This MR can't add the appropriate Markdownlint rule to enforce it via the MD034 rule, because the tooling breaks on our redirect syntax and our embedded Youtube video documentation.

Still worth merging, because it takes many links from not hyperlinking to hyperlinking.

CC @gl-docsteam

Author's checklist

  • Follow the Documentation Guidelines and Style Guide.
  • Link docs to and from the higher-level index page, plus other related docs where helpful.
  • Apply the ~Documentation label.

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set and that you merge the equivalent EE MR before the CE MR if both exist.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by Evan Read

Merge request reports