QuantEcon / QuantEcon/scipy_tutorial_2026
CI fails on Netlify preview deploy: NETLIFY_AUTH_TOKEN / NETLIFY_SITE_ID not set
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Summary
The Build Project [using jupyter-book] workflow (ci.yml) fails on every PR — but not because of the build. The jupyter-book build succeeds; the job dies on its final step, Preview Deploy to Netlify, because the required secrets are not configured in this repo.
Evidence
From the failed run on PR #1 (run 26938631605), step conclusions:
success Build Download Notebooks (sphinx-tojupyter)
success Build HTML
success Install Node.js
failure Preview Deploy to Netlify <-- only failure
Error message:
Error: Authentication required. NETLIFY_AUTH_TOKEN is not set and
`netlify login --request <message>` can be used to authenticate.
##[error]Process completed with exit code 1.
gh secret list for the repo returns nothing — no Actions secrets are configured. The step at .github/workflows/ci.yml (Preview Deploy to Netlify) passes secrets.NETLIFY_AUTH_TOKEN and secrets.NETLIFY_SITE_ID, which are empty, so the Netlify CLI exits 1 and the whole job goes red.
Impact
- Pre-existing and repo-wide — affects every PR (e.g. #1 and #3), unrelated to the content of any individual PR. The lectures themselves build cleanly.
- Because the job goes red, the build result is masked by an infrastructure step, which makes it hard to tell at a glance whether a real build break has occurred.
(There is also a separate older failure on main in the Build & Publish to GH Pages workflow — likely the same class of missing-config/secret issue — worth a look while we're here, but tracked separately if needed.)
Options to resolve
- Add the secrets (enables PR previews) — a repo/org admin sets
NETLIFY_AUTH_TOKENandNETLIFY_SITE_IDunder Settings → Secrets and variables → Actions. The QuantEcon org already uses Netlify previews on the other lecture repos, so a token should exist. - Guard the step so CI is green when the token is absent (e.g. forks / before secrets land):
(Secrets can't be referenced directly in- name: Preview Deploy to Netlify if: ${{ env.NETLIFY_AUTH_TOKEN != '' }} env: NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }} # ...if:, so map toenvfirst, then testenv.) - Remove the Netlify preview step if previews aren't wanted for this repo.
Recommended: option 1 if we want previews here, with option 2 as a resilience improvement regardless so the build remains the real pass/fail signal.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/ci.yml lines 79-85 and the failed run linked in the issue. Confirm how the Preview Deploy to Netlify step receives its secrets and how the preceding build steps report success. Done means the workflow’s intended preview or missing-secret behavior is explicit, while the Jupyter Book build remains the meaningful CI result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, yaml
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100