The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation status

16 Strings
0%
Browse Translate
456 Words
0%
2,879 Characters
0%

Strings status

Strings Words Characters
16 456 2,879
All strings Browse Translate Zen
16 456 2,879
Unfinished strings Browse Translate Zen
16 456 2,879
Strings marked for edit Browse Translate Zen
1 80 482
Strings with any failing checks Browse Translate Zen
1 80 482
Failing check: Mismatched full stop Browse Translate Zen
1 80 482
Failing check: Mismatched question mark Browse Translate Zen

Summary

Project website tuist.dev
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses monolingual files.
  • The translation base language can not be edited.
Source code repository https://github.com/tuist/tuist
Repository branch main
Last remote commit feat(kura): declare the analytics-outbox RocksDB column family (#13467) 706c0d9811
Pedro Piñera Buendía authored 09/22/2026
Last commit in Weblate Translated using Weblate (Chinese (Traditional Han script)) 00c4608470
DeepL authored 09/21/2026
Weblate repository https://translate.tuist.dev/git/tuist/documentation-pages/
File mask docs/docs/*/contributors/code-reviews.md
Monolingual base language file docs/docs/en/contributors/code-reviews.md
Translation file Download docs/docs/zh_Hant/contributors/code-reviews.md
Last change Aug. 26, 2026, 3:55 p.m.
Last change made by Background commit
Language Chinese (Traditional Han script)
Language code zh_Hant
Text direction Left to right
Case sensitivity Case-insensitive
Number of speakers 39,078,482
Number of plurals 1
Plural type None
Plurals
Plural formula 0
08/26/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 16 456 2,879
Translated 0% 0 0% 0 0% 0
Needs editing 100% 16 100% 456 100% 2,879
Read-only 0% 0 0% 0 0% 0
Failing checks 6% 1 17% 80 16% 482
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 35 changes 0 changes 14 changes 0 changes 2 changes 0 changes 0 changes 0 changes 9 changes 0 changes 0 changes 0 changes 7 changes 0 changes 4 changes 0 changes 7 changes
SepOctNovDecJanFebMarAprMayJunJulAug

Quick numbers

456
Hosted words
16
Hosted strings
0%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
—
Translated
—
—
Contributors
—
User avatar weblate:commit

Changes committed
Changes committed 08/26/2026
User avatar mt:deepl

Automatically translated
Breaking changes are a bad user experience for users of Tuist. Contributions should avoid introducing breaking changes unless it’s strictly necessary. There are many language features that we can leverage to evolve the interface of Tuist without resorting to a breaking change. Whether a change is breaking or not might not be obvious. A method to verify whether the change is breaking is running Tuist against the fixture projects in the fixtures directory. It requires putting ourselves in the user’s shoes and imagine how the changes would impact them.
破壞性變更會為 Tuist 使用者帶來糟糕的使用體驗。除非絕對必要，否則貢獻者應避免引入破壞性變更。我們可以利運用許多語言功能特性來演進 Tuist 的介面，而無需訴諸破壞性變更。某項變更是否屬於破壞性變更，有時可能並不顯而易見。 驗證變更是否會造成導致相容性問題的方法之一，是將 Tuist 套用至與 fixtures 目錄中的測試專案進行對照測試。這需要我們設身處地站在使用者的角度，設想這些變更會對他們造成什麼影響。
08/26/2026
User avatar mt:deepl

Automatically translated
Tests allow changing code with confidence. The code on pull requests should be tested, and all tests should pass. A good test is a test that consistently produces the same result and that it’s easy to understand and maintain. Reviewers spend most of the review time in the implementation code, but tests are equally important because they are code too.
測試能讓人有信心修改程式碼。拉取請求中的程式碼應經過測試，且所有測試都應通過。好的測試應能始終產生相同結果，並且容易且易於理解與維護。審查閱者雖將大部分審查閱時間花在實作程式碼上，但測試同樣重要，因為它們也是程式碼的一部分。
08/26/2026
User avatar mt:deepl

Automatically translated
Reviewing pull requests is a common type of contribution. Despite continuous integration (CI) ensuring the code does what’s supposed to do, it’s not enough. There are contribution traits that can’t be automated: design, code structure & architecture, tests quality, or typos. The following sections represent different aspects of the code review process.
審閱拉取請求（pull requests）是一種常見的貢獻形式。儘管持續整合（CI）能確保程式碼能運作如預期運作，但這還不夠。有些貢獻特質無法透過自動化處理，例如：設計、程式碼結構與架構、測試品質，或是錯字。以下各節將介紹探討程式碼審閱流程的不同面向。
08/26/2026
User avatar mt:deepl

Automatically translated
Large pull requests are hard to review and it’s easier to miss out details. If a pull request becomes too large and unmanageable, suggest the author to break it down.
大型拉取請求（pull request）難以審查，且容易遺漏忽略細節。若拉取請求過於龐大且而難以管理，請建議作者將其拆分為多個部分。
08/26/2026
User avatar mt:deepl

Automatically translated
---
{
"title": "Code reviews",
"titleTemplate": ":title · Contributors · Tuist",
"description": "Learn how to contribute to Tuist by reviewing code"
}
---
---
{
"title": "程式碼審查",
"titleTemplate": ":title · 貢獻者 · Tuist",
"description": "了解如何透過審查程式碼為 Tuist 做出貢獻心力"
}
---
08/26/2026
User avatar mt:deepl

Automatically translated
Does the code express its intention clearly? **If you need to spend a bunch of time figuring out what the code does, the code implementation needs to be improved.** Suggest splitting the code into smaller abstractions that are easier to understand. Alternative, and as a last resource, they can add a comment explaining the reasoning behind it. Ask yourself if you’d be able to understand the code in a near future, without any surrounding context like the pull request description.
這段程式碼是否清楚地表達了其意圖？**若您需要花費大量時間才能弄清楚程式碼的功能，則該程式碼的實作需要改進。** 建議將程式碼拆分為更小、更易於理解的抽象單元。另一種方法（且作為最後的手段），可以添加註解來解釋其背後的邏輯。請自問：在不久的將來，若沒有拉取請求說明等周邊上下文背景資訊，您是否仍能理解這段程式碼？
08/26/2026
User avatar weblate:commit

Changes committed
Changes committed 07/26/2026
User avatar mt:deepl

Automatically translated
Does the code express its intention clearly? **If you need to spend a bunch of time figuring out what the code does, the code implementation needs to be improved.** Suggest splitting the code into smaller abstractions that are easier to understand. Alternative, and as a last resource, they can add a comment explaining the reasoning behind it. Ask yourself if you’d be able to understand the code in a near future, without any surrounding context like the pull request description.
這段程式碼是否清楚地表達了其意圖？**若您需要花費大量時間才能弄清楚程式碼的功能，則該程式碼的實作需要改進。** 建議將程式碼拆分為更小、更易於理解的抽象單元。另一種方法（且作為最後的手段），可以添加註解來解釋其背後的邏輯。請自問：在不久的將來，若沒有拉取請求說明等周邊背景資訊上下文，您是否仍能理解這段程式碼？
07/26/2026
User avatar mt:deepl

Automatically translated
Tests allow changing code with confidence. The code on pull requests should be tested, and all tests should pass. A good test is a test that consistently produces the same result and that it’s easy to understand and maintain. Reviewers spend most of the review time in the implementation code, but tests are equally important because they are code too.
測試能讓人有信心修改程式碼。拉取請求中的程式碼應經過測試，且所有測試都應通過。一份好的測試，應能始終產生相同結果，且易於並且容易理解與維護。審查者雖將大部分審查時間花在實作程式碼上，但測試同樣重要，因為它們也是程式碼的一部分。
07/26/2026
Browse all translation changes