fix: enable CI checks to run from devcontainer - #1136
Open
vdstrizhkova wants to merge 1 commit into
Open
Conversation
- Add Docker-in-Docker feature and run-megalinter.sh script so MegaLinter can be executed locally via .devcontainer/run-megalinter.sh - Update devcontainer base image to devcontainers/python:1 and remove stale Yarn apt repository that causes apt-get update failures - Pin Pygments<2.20 in requirements-docs.txt to fix mkdocs build: Pygments 2.20.0 calls html.escape() on a filename option that pymdownx can pass as None, causing AttributeError during documentation build - Accept HTTP 403/429 in lychee.toml to prevent false-positive link failures from GitHub rate-limiting and bot-protection in CI; also exclude known bot-blocking domains
vdstrizhkova
requested review from
TessFerrandez,
nyouens and
shiranr
as code owners
July 21, 2026 07:15
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What are you trying to address
This PR makes all CI checks runnable from the devcontainer, so contributors can validate their changes locally before pushing.
Changes:
.devcontainer/devcontainer.json— Adds thedocker-in-dockerdevcontainer feature, required to run the MegaLinter Docker image from inside the devcontainer. Also migrates settings to the currentcustomizations.vscodeschema and adds thems-azuretools.vscode-dockerextension..devcontainer/devcontainer-lock.json— New lock file pinning thedocker-in-dockerfeature tov2.17.0for reproducible builds..devcontainer/Dockerfile— Updates the base image tomcr.microsoft.com/devcontainers/python:1-${VARIANT}and removes a stale Yarn apt repository that causedapt-get updatefailures..devcontainer/run-megalinter.sh— New helper script that mirrors the MegaLinter CI step locally. Runningbash .devcontainer/run-megalinter.shscans only changed files (matchingVALIDATE_ALL_CODEBASE: falsein CI);VALIDATE_ALL_CODEBASE=true bash .devcontainer/run-megalinter.shscans everything.requirements-docs.txt— PinsPygments>=2,<2.20to avoid anAttributeErrorintroduced in Pygments 2.20.0, which caused the mkdocs build to crash whenpymdownx.highlightpassesfilename=NonetoHtmlFormatter.lychee.toml— Accepts HTTP 403 and 429 responses in addition to 2xx, preventing false-positive link-check failures on sites (including GitHub) that block automated crawlers. Also removes an invalidheadertable entry and excludes additional bot-blocking domains.Checklist