Allow Codespaces/Gitpod container startup, even if site build fails the --strict
mode tests
#463
Labels
enhancement
New feature or request
--strict
mode tests
#463
What would you like to be able to do?
A recent Codespaces container creation failed with:
The Codespace I'm trying to start is the one where I'm deleting the
index.md
file, as we're moving that to the main repository. Themkdocs build
fails, as it should, and warns me about the broken links: 🙃Here's the full log (except the recovery container logs, as those are not relevant here).
Select me to see logs
I think the main thing we should change is make it so that the devcontainer/codespace is always alllowed to start, even if there are problems with the docs site generation.
Did you already have any implementation ideas?
I think we need to make it so the
--strict
mode ofmkdocs
does not apply to the Codespaces/Gitpod/Devcontainer startup sequence.We should keep the strict mode on for the official builds, and for the checks we run on any incoming PRs!
Do you want to write this feature yourself?
No
The text was updated successfully, but these errors were encountered: