Canary: bring its `ci.yml`, `cache.yml` and `publish.yml` back in line with `templates/`

Aperta
  • Qualcosa non va?
#310 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
39/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, shell
Ambito
ci-cd

Direzione di ricerca

Start by comparing the canary workflows with their counterparts in templates/: ci.yml, cache.yml, and publish.yml. Read #100, #230, and the overlapping #302 to understand the referenced changes and the open decisions about intentional differences and keeping both in step. Done means the canary and templates are aligned where intended, with those differences and an ongoing sync approach settled.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

infrastructure low-priority

Carried from #100 when it closed (its Stage 2). The canary, QuantEcon/test-actions-lecture-intro, is meant to show what a repository that copies templates/ gets. Its three workflows differ from the templates (checked 2026-11-10):

Workflow templates/ The canary
ci.yml On pull_request to main. Four jobs: the placeholder comment, the build, a separate deploy job, and the PDF check (#230). Restores the execution cache On pull_request and workflow_dispatch. One job, which builds and deploys. Restores the build cache
cache.yml Weekly on Sunday at 00:00 UTC, by hand, and on a push to main that changes environment.yml Weekly on Sunday at 03:00 UTC, and by hand
publish.yml On a push to main, and by hand. The build and the deploy are separate jobs On a publish* tag only, in one job

So a change to a template reaches no real run until a consumer copies it. Two things to settle when this is picked up:

  • Which differences the canary keeps on purpose. Its publish* tag stops Pages redeploying on every push, and the release gate now deploys the same Pages site from the canary's main.
  • How the two stay in step afterwards.

This overlaps #302, which schedules the canary's ci.yml and publish.yml, so the two are best done together. Low priority.

Claude Code (on behalf of mmcky)

Lingua principale
Shell
Stelle
0
Fork
1
Merge medio
18h 51m
PR unite (30g)
58

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di QuantEcon/actions

Tutte le issue di QuantEcon/actions

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.