Every pull request here carries four red Netlify checks — netlify/beautiful-dodol-cb9543/deploy-preview, Header rules, Redirect rules and Pages changed — and they have failed on every recent PR (#67, #68, #72) while the site's real preview works. A permanently red column trains reviewers to ignore it.
Cause
The repository has two preview mechanisms wired and only one is intended.
The intended one is in .github/workflows/ci.yml: the build-and-deploy job builds the site in Actions and pushes lectures/_build/html/ with the Netlify CLI, authenticating with the NETLIFY_SITE_ID and NETLIFY_AUTH_TOKEN secrets, then posts the "Netlify Preview Ready" comment. That path works: on #72 it produced https://pr-72--beautiful-dodol-cb9543.netlify.app.
The failing one is Netlify's own GitHub App integration. The Netlify site is also linked to this repository for continuous deployment, so on every PR Netlify clones the repo and tries to build it on its own servers, where there is no build command and no mystmd. That build fails and the App posts the four statuses. The failing deploy (6a9e03219fea66000810374e on #72) is a different deploy from the CLI one, which is how the two show up side by side.
Fix
This is a Netlify dashboard setting, not a repository change. In the site's configuration under Build & deploy → Continuous deployment, unlink the repository. The CLI deploys keep working because they do not depend on a linked repo. If the link is wanted for some other reason, the narrower alternatives are to stop builds in that same section, or to delete the GitHub commit-status entries under Notifications → Deploy notifications.
A repository-side netlify.toml is not a clean substitute: a [build] ignore script would skip Netlify's build but may still report a status, and giving Netlify a real build command would duplicate the Actions build and need mystmd installed there.
Acceptance
- A new PR shows only
build-and-deploy, data-url-guard and the Copilot review as checks.
- The "Netlify Preview Ready" comment and its URL still appear.
Every pull request here carries four red Netlify checks —
netlify/beautiful-dodol-cb9543/deploy-preview,Header rules,Redirect rulesandPages changed— and they have failed on every recent PR (#67, #68, #72) while the site's real preview works. A permanently red column trains reviewers to ignore it.Cause
The repository has two preview mechanisms wired and only one is intended.
The intended one is in
.github/workflows/ci.yml: thebuild-and-deployjob builds the site in Actions and pusheslectures/_build/html/with the Netlify CLI, authenticating with theNETLIFY_SITE_IDandNETLIFY_AUTH_TOKENsecrets, then posts the "Netlify Preview Ready" comment. That path works: on #72 it produced https://pr-72--beautiful-dodol-cb9543.netlify.app.The failing one is Netlify's own GitHub App integration. The Netlify site is also linked to this repository for continuous deployment, so on every PR Netlify clones the repo and tries to build it on its own servers, where there is no build command and no
mystmd. That build fails and the App posts the four statuses. The failing deploy (6a9e03219fea66000810374eon #72) is a different deploy from the CLI one, which is how the two show up side by side.Fix
This is a Netlify dashboard setting, not a repository change. In the site's configuration under Build & deploy → Continuous deployment, unlink the repository. The CLI deploys keep working because they do not depend on a linked repo. If the link is wanted for some other reason, the narrower alternatives are to stop builds in that same section, or to delete the GitHub commit-status entries under Notifications → Deploy notifications.
A repository-side
netlify.tomlis not a clean substitute: a[build] ignorescript would skip Netlify's build but may still report a status, and giving Netlify a real build command would duplicate the Actions build and needmystmdinstalled there.Acceptance
build-and-deploy,data-url-guardand the Copilot review as checks.