QuantEcon / QuantEcon/lecture-dp
publish: pass `cname` to cut over from the interim github.io URL to the custom domain
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
Surfaced by the QuantEcon/actions v0.8.0 validation study.
Context
lecture-dp is the one composite-migrated repo still serving on the interim github.io URL. Its publish step (.github/workflows/publish.yml:69) calls quantecon/actions/publish-gh-pages@v0.8.0 without a cname, so it's not exercising the custom-domain path in production. This is a deliberate interim state, not a defect.
When ready
Pass the custom domain to publish-gh-pages to cut over:
- uses: quantecon/actions/publish-gh-pages@v0.8.0
with:
cname: dp.quantecon.org # confirm the intended domain
# ...existing inputs
Confirm the exact domain — the other lecture sites follow <name>.quantecon.org (e.g. jax.quantecon.org, python-advanced.quantecon.org).
Context: QuantEcon/lectures#11 (v0.8.0 standardization).
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
Open .github/workflows/publish.yml around line 69 and inspect the publish-gh-pages step. Compare the intended custom-domain pattern with the other lecture-site examples named in the issue, confirm the exact domain with the repository context, and pass it as cname. Done means the workflow uses the confirmed dp.quantecon.org domain for publishing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 78/100