Link checking on translated documentation

What does this MR do?

This MR is adding a docs-i18n-lint links CI job checks the validity of relative links in the i18n documentation site whos content lives in /doc-locale. It is the same as docs-lint links CI that checks /docs.

The difference in the two, is the docs-i18n-lint links is triggered manually, and allowed to fail. Until technical documentation is 100% translated and continuous localization is on we expect some relative links to break. But we want to know what links are failing are this CI will provide us a tool for getting that information.

Screenshot_2025-11-11_at_3.40.03_PM

Related issues

Related gitlab-com/localization/docs-site-localization#734

Related gitlab-com/localization/docs-site-localization#333 (closed)

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • MR title and description are up to date, accurate, and descriptive.
  • MR targeting the appropriate branch.
  • Latest Merge Result pipeline is green.
  • When ready for review, MR is labeled workflowready for review per the Distribution MR workflow.

For GitLab team members

If you don't have access to this, the reviewer should trigger these jobs for you during the review process.

  • The manual Trigger:ee-package jobs have a green pipeline running against latest commit.
  • If config/software or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
  • If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline must succeed.
  • If CI configuration is changed, the branch must be pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes.
  • Documentation created/updated - To be added to this or as a follow up
  • Tests added.
  • Integration tests added to GitLab QA.
  • Equivalent MR/issue for the GitLab Chart opened.
  • Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.
Edited by Lauren Barker

Merge request reports

Loading