google/comprehensive-rust

Add CI job that ensures every translation builds

Open

#2,539 建立於 2025年1月4日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)Rust (32,954 star) (2,009 fork)batch import
enhancementgood first issue

描述

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

貢獻者指南

技術棧
github actions
領域
ci cd
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
GitHub ActionsYAMLRust translation workflow
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
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.