Skip to content

Run MKDocs strict validation on new commit pushes.#5173

Merged
lrcouto merged 15 commits intomainfrom
linkcheck-mkdocs
Oct 24, 2025
Merged

Run MKDocs strict validation on new commit pushes.#5173
lrcouto merged 15 commits intomainfrom
linkcheck-mkdocs

Conversation

@lrcouto
Copy link
Contributor

@lrcouto lrcouto commented Oct 21, 2025

Description

#5171

We want to run stricter validation on MKDocs to prevent broken links and anchors.

This PR introduces a new CI job that builds MKDocs with the --strict flag to check for broken links and anchors. It also changes MKDocs configuration adding:

validation:
  omitted_files: warn
  absolute_links: warn
  unrecognized_links: warn
  anchors: warn

So all of those things throw warnings, and will cause the CI to fail.

Finally, several broken internal links and other warnings thrown by mkdocs build --strict have been fixed.

Development notes

Developer Certificate of Origin

We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a Signed-off-by line in the commit message. See our wiki for guidance.

If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.

Checklist

  • Read the contributing guidelines
  • Signed off each commit with a Developer Certificate of Origin (DCO)
  • Opened this PR as a 'Draft Pull Request' if it is work-in-progress
  • Updated the documentation to reflect the code changes
  • Added a description of this change in the RELEASE.md file
  • Added tests to cover my changes
  • Checked if this change will affect Kedro-Viz, and if so, communicated that with the Viz team

Signed-off-by: Laura Couto <laurarccouto@gmail.com>
Signed-off-by: Laura Couto <laurarccouto@gmail.com>
@lrcouto lrcouto marked this pull request as ready for review October 21, 2025 03:28
@lrcouto lrcouto requested a review from merelcht as a code owner October 21, 2025 03:28
@lrcouto lrcouto marked this pull request as draft October 21, 2025 03:29
lrcouto and others added 9 commits October 21, 2025 00:48
Signed-off-by: Laura Couto <laurarccouto@gmail.com>
Signed-off-by: Laura Couto <laurarccouto@gmail.com>
Signed-off-by: Laura Couto <laurarccouto@gmail.com>
Signed-off-by: Laura Couto <laurarccouto@gmail.com>
Signed-off-by: Laura Couto <laurarccouto@gmail.com>
Signed-off-by: Laura Couto <laurarccouto@gmail.com>
Signed-off-by: Laura Couto <laurarccouto@gmail.com>
Signed-off-by: Laura Couto <laurarccouto@gmail.com>
@lrcouto
Copy link
Contributor Author

lrcouto commented Oct 23, 2025

Language linter started failing after I fixed the broken anchors because apparently the word "alternatively" (which was there before) is "too wordy". I'm electing to ignore that. =p

Signed-off-by: Laura Couto <laurarccouto@gmail.com>
@lrcouto lrcouto changed the title Add linkcheck job to github CI Run MKDocs strict validation on new commit pushes. Oct 23, 2025
@lrcouto lrcouto marked this pull request as ready for review October 23, 2025 03:16
@lrcouto lrcouto requested a review from yetudada as a code owner October 23, 2025 03:16
Copy link
Contributor

@rashidakanchwala rashidakanchwala left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Laura!

Copy link
Member

@merelcht merelcht left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The setup looks good! I left some comments for the links. Let's try still make them point to specific sections where possible.


strategy:
matrix:
python-version: [ "3.10", "3.11", "3.12", "3.13" ]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to run this for every python version. Let's just do the same as for the lint jobs: 3.11

## Configure `kedro run` arguments

The [Kedro CLI documentation](../getting-started/commands_reference.md#run-the-project) lists the available CLI options for `kedro run`. You can alternatively supply a configuration file that contains the arguments to `kedro run`.
The [Kedro CLI documentation](../getting-started/commands_reference.md) lists the available CLI options for `kedro run`. You can alternatively supply a configuration file that contains the arguments to `kedro run`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this link to https://docs.kedro.org/en/1.0.0/getting-started/commands_reference/#kedro-run ?


### How to change the configuration source folder at runtime
Specify a source folder for the configuration files at runtime using the [`kedro run` CLI command](../getting-started/commands_reference.md#modifying-a-kedro-run) with the `--conf-source` flag as follows:
Specify a source folder for the configuration files at runtime using the [`kedro run` CLI command](../getting-started/commands_reference.md#kedro-commands) with the `--conf-source` flag as follows:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


## Package-based
If you prefer not to use containerisation, you can instead package your Kedro project using [`kedro package`](../getting-started/commands_reference.md#deploy-the-project).
If you prefer not to use containerisation, you can instead package your Kedro project using [`kedro package`](../getting-started/commands_reference.md#kedro-commands).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

* [How do I specify additional configuration environments](../configure/configuration_basics.md#how-to-specify-additional-configuration-environments)?
* [How do I change the default overriding configuration environment](../configure/configuration_basics.md#how-to-change-the-default-overriding-environment)?
* [How do I use only one configuration environment](../configure/configuration_basics.md#how-to-use-only-one-configuration-environment)?
* [How do I use Kedro without the rich library](../configure/configuration_basics.md#how-to-use-kedro-without-the-rich-library)?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I saw this one, but I thought it'd be weird to put a link from the logging section in there when all of the other links are from the configuration section. Do you think it'd still be relevant?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's still a good link to have on the getting started FAQ. It might be harder to find for people otherwise.

Signed-off-by: Laura Couto <laurarccouto@gmail.com>
Copy link
Member

@merelcht merelcht left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 👍

lrcouto and others added 2 commits October 24, 2025 13:12
Co-authored-by: Merel Theisen <49397448+merelcht@users.noreply.github.com>
Signed-off-by: L. R. Couto <57910428+lrcouto@users.noreply.github.com>
Co-authored-by: Merel Theisen <49397448+merelcht@users.noreply.github.com>
Signed-off-by: L. R. Couto <57910428+lrcouto@users.noreply.github.com>
@lrcouto lrcouto merged commit 6a94c02 into main Oct 24, 2025
37 of 38 checks passed
@lrcouto lrcouto deleted the linkcheck-mkdocs branch October 24, 2025 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants