Phase 1 quick wins: bounded SHA fetches, concurrency-group fallback, paths-ignore in templates/ci.yml
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 1
- Avg merge
- 32m
- Merged PRs (30d)
- 3
Description
The "one small actions-repo PR" bundle from #92 Phase 1 — three independent quick wins, all in this repo:
-
--depth=1on the two still-unbounded SHA fetches inscripts/detect-changed-lectures.sh:26-27. Shippable today;lecture-python.mysthas no copy of the script (it callspreview-netlify@v0, which invokes ours), so only the checkout side is consumer work — tracked with the consumer items. - Concurrency cancellation fallback in
templates/ci.yml:24-26:group: ci-${{ github.event.pull_request.number || github.run_id }}. The template has the group andcancel-in-progress: truebut not the fallback, and the fallback is load-bearing: both consumers also trigger onworkflow_dispatch, so a verbatim copy puts every manual run in the empty groupci-, cancelling each other. Also closes a stale-overwrite hazard. - Paths filters (
paths-ignorefail-open variant) intemplates/ci.ymlso docs-only PRs skip the preview — the template has nopathskey at all.
Related, deliberately not here: the CLI-install gate on pull_request for both preview actions folds into #105 (same two steps it wants pinned — one PR, not two); the zstd/tag-input item stays separate because :zstd must be validated before :latest moves.
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 with scripts/detect-changed-lectures.sh:26-27 and templates/ci.yml:24-26, then inspect the template's workflow triggers and its two consumers. Add bounded SHA fetches, the pull-request-number/run-id concurrency fallback, and a fail-open paths-ignore filter so docs-only pull requests skip previews without collapsing manual runs. Done means all three checklist items are reflected in the reusable template and script.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100