google/comprehensive-rust

Add CI job that ensures every translation builds

Open

#2,539 opened on 2025年1月4日

GitHub で見る
 (2 comments) (0 reactions) (0 assignees)Rust (32,954 stars) (2,009 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.