Run MKDocs strict validation on new commit pushes.#5173
Conversation
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>
Signed-off-by: Laura Couto <laurarccouto@gmail.com>
|
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>
merelcht
left a comment
There was a problem hiding this comment.
The setup looks good! I left some comments for the links. Let's try still make them point to specific sections where possible.
.github/workflows/docs-linkcheck.yml
Outdated
|
|
||
| strategy: | ||
| matrix: | ||
| python-version: [ "3.10", "3.11", "3.12", "3.13" ] |
There was a problem hiding this comment.
No need to run this for every python version. Let's just do the same as for the lint jobs: 3.11
docs/build/run_a_pipeline.md
Outdated
| ## 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`. |
There was a problem hiding this comment.
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: |
There was a problem hiding this comment.
I think this should also link to : https://docs.kedro.org/en/1.0.0/getting-started/commands_reference/#kedro-run
docs/deploy/single_machine.md
Outdated
|
|
||
| ## 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). |
There was a problem hiding this comment.
| * [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)? |
There was a problem hiding this comment.
I think this just moved to https://docs.kedro.org/en/1.0.0/develop/logging/#how-to-use-logging-without-the-rich-library
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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>
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>
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
--strictflag to check for broken links and anchors. It also changes MKDocs configuration adding: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 --stricthave 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-byline 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
RELEASE.mdfile