CI: miroir GitHub — meme restructuration (split + rust-cache) #233
Labels
No labels
autopilot:pending-human
source:analyste
source:defenseur
source:human
source:medic
status:approved
status:blocked
status:in-progress
status:needs-clarification
status:needs-fix
status:ready
status:review
status:triage
type:bug
type:feature
type:infra
type:refactor
type:schema
type:security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: maximus/Simpl-Resultat#233
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs: spec-decisions-ci-build-optimization.md + spec-plan-ci-build-optimization.md
Mettre le miroir GitHub en coherence avec Forgejo (convention "kept in sync").
.github/workflows/check-rust.yml+check-frontend.ymlen miroir : runnersubuntu-latest,dtolnay/rust-toolchain@stable,actions/setup-node(cache npm),Swatinem/rust-cache@v2, envCARGO_INCREMENTAL: 0. PAS d'etape cargo-audit (absente du miroir).on.pull_request.pathsque cote Forgejo (rust vs frontend)..github/workflows/check.yml.uses:en forme courte GitHub (actions/checkout@v4, etc.).Depends on #232.
Retirée du scope suite à /review-spec (2026-06-30).
Analyse d'impact : le check.yml du miroir GitHub ne se déclenche quasiment jamais — toutes les PR se font sur Forgejo, et un push-mirror ne crée pas de PR (donc aucun événement
pull_requestcôté GitHub). L'optimiser n'apporte aucun gain pratique..github/workflows/est laissé tel quel.Voir spec-decisions-ci-build-optimization.md → « Décisions tranchées à la revue ».