lecture-dp: save-cache one-liner, cache-on-merge job, shallow checkout
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Shell
- Stars
- 0
- Forks
- 1
- Avg merge
- 32m
- Merged PRs (30d)
- 3
Description
The lecture-dp consumer items from #92 Phase 1. Work lands in QuantEcon/lecture-dp.
-
save-cache: 'true'on the restore step (one line). Itsci.ymlstill callsquantecon/actions/restore-jupyter-cache@v0without it. The input exists since v0.5.2 (#24), the save-mode outputs/fail-on-missbugs were fixed by #104 in v0.9.0, and the path is CI-covered since v0.10.0 — nothing blocks it. - Cache-on-merge job on push to main (
paths-ignore: [environment.yml]; the weekly rebuild stays the anchor; no actions-repo change). Itscache.ymltriggers on the weekly cron pluspush: paths: [environment.yml]— the inverse of what this needs. -
fetch-depth: 1on theci.yml:19checkout (stillfetch-depth: 0) — land together with the bounded-fetch change in the actions-repo quick-wins PR (#147).
Contributor guide
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 in the lecture-dp consumer's ci.yml, including checkout line 19, and its cache.yml; compare the requested cache input, push trigger, and fetch depth with the existing workflows. Review the actions-repo quick-wins PR #147 before changing the checkout setting. Done means the restore step saves the cache, main pushes trigger the cache job while ignoring environment.yml, and checkout uses depth 1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100