Organisation-wide files for github.com/mgpl-diagnostics.
profile/README.mdis the organisation's profile page.profile/banner.svgis generated byscripts/make-banner.mjs. Text is converted to vector paths from the Manrope font, and the logo comes from report-kit. Run the script inside the local MGPL workspace.profile/avatar.pngis the organisation's profile picture, generated byscripts/make-avatar.mjs(the logo's drop icon on the banner's navy). GitHub has no API for it: upload it in the org settings → Profile.scripts/protect-repos.mjsapplies the repository rules to every repo (PR-onlymain, required CI and code-owner review, maintainer-only release tags, private vulnerability reporting). Re-run it after creating or publishing a repo:node scripts/protect-repos.mjs(add--dry-runto preview)..github/holds the default community files every repo inherits: issue forms, PR template, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT and SUPPORT.actions/holds the CI building blocks every repo'scijob uses (composite actions, so the required check keeps its nameci):actions/node: Node.js 22, the npm download cache, GitHub Packages auth (github-packages: "true"), the MongoDB binary cache (mongodb: "true"), then the install command;actions/apt: Ubuntu packages from cached.debfiles keyed on the runner image, with retries and a time limit on a cache miss.
.github/workflows/docker-build.ymlis a reusable workflow: it builds a repo's Dockerfile without pushing, with layer caching and an optional smoke test (the api and the dashboard call it on every PR). Releases still push from each repo'srelease.yml.- Changing anything in
actions/ordocker-build.ymlchanges every repo's CI on its next run: open a PR here, then re-run one kit's CI from the PR branch (uses: …@<branch>) before merging. llms-full.txt:node scripts/llms-full.mjs "mgpl-diagnostics/.github" README.md .github llms.txt profile scripts actions.