google/comprehensive-rust

Add CI job that ensures every translation builds

Open

#2 539 ouverte le 4 janv. 2025

Voir sur GitHub
 (2 commentaires) (0 réactions) (0 assignés)Rust (32 954 stars) (2 009 forks)batch import
enhancementgood first issue

Description

Currently, I have to add each language individually to the branch protection rules for main. This a problem since we can merge PRs which fail later when building the translations for publishing.

I think we can handle this by adding a new CI job which waits on every translation and only succeeds when they all succeed.

Originally posted by @mgeisler in https://github.com/google/comprehensive-rust/issues/2531#issuecomment-2571282773

Guide contributeur

Stack technique
github actions
Domaine
ci cd
Type d'issue
feature
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
3
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
1-3 hours
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
fresh
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
clear
Prérequis
GitHub ActionsYAMLRust translation workflow
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
70
Direction de recherche
Refer to the existing translation build CI jobs in the repository (e.g., .github/workflows/ directory). The issue references comment #2531 which likely contains more context. The goal is to create a new job that depends on all translation jobs and succeeds only when they all succeed. Look for how translation jobs are currently defined and how to aggregate their statuses. Consider using GitHub Actions' job dependencies and conditional steps.