The translation is temporarily closed for contributions due to maintenance, please come back later.
Please sign in to see the alerts.

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 fix(cli): pin Colorizer as a registry dependency in Package.resolved (#12178) 27cc665ad6
Pedro Piñera Buendía authored 07/31/2026
Last commit in Weblate Translated using Weblate (Turkish) 352dfe9c3b
DeepL authored 07/29/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
07/26/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 192 5,472 34,548
Source 16 456 2,879
Translated 58% 113 58% 3,193 58% 20,156
Needs editing 41% 79 41% 2,279 41% 14,392
Read-only 8% 16 8% 456 8% 2,879
Failing checks 16% 32 6% 340 6% 2,387
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 245 changes 0 changes 117 changes 0 changes 566 changes 0 changes 141 changes 0 changes 29 changes 0 changes 30 changes 0 changes 48 changes 0 changes 0 changes 0 changes 34 changes
JulAugSepOctNovDecJanFebMarAprMayJun

Quick numbers

5,472
Hosted words
192
Hosted strings
58%
Translated
7
Contributors
0
Components
12
Languages
12
Translations
0
Screenshots
and previous 30 days

Trends of last 30 days

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

Changes committed
Changes committed 07/26/2026
User avatar weblate:commit

Changes committed
Changes committed 07/26/2026
User avatar weblate:commit

Changes committed
Changes committed 07/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
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）能確保程式碼運作能如預期運作，但這還不夠。有些貢獻特質無法透過自動化處理，例如：設計、程式碼結構與架構、測試品質，或是錯字。以下各節將介紹程式碼審閱流程的不同面向。
07/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.
Uyumsuzluk yaratan değişiklikler, Tuist kullanıcıları için kötü bir kullanıcı deneyimi yaratıoluşturur. Katkılar, kesinlikle gerekli olmadıkça uyumsuzluk yaratan değişiklikler getirmekten kaçınmalıdır. Uyumsuzluk yaratan bir değişikliğe başvurmadan Tuist'in arayüzünü geliştirmek için yararlanabileceğimiz birçok dil özelliği vardır. Bir değişikliğin uyumsuz olup olluk yaratıp yaratmadığı her zaman açık olmayabilir. Değişikliğin kırıcı olup olmadığını doğrulamanın bir yolu, Tuist’i fixtures dizinindeki test projeleriyle çalıştırmaktır. Bunun için kendimizi kullanıcının yerine koymalı ve değişikliklerin onkullanıcıları nasıl etkileyeceğini hayal etmeliyiz.
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.
Kod, amacını net bir şekilde ifade ediyor mu? **Kodun ne işe yaradığını anlamak için çok fazla zaman harcamanız gerekiyorsa, kodun uygulanış şekli iyileştirilmelidir.** Kodu, anlaşılması daha kolay olan daha küçük soyutlamalara bölmeniziparçalara ayırmayı öneririzn. Alternatif olarak ve son çare olarak, kodun arkasındaki mantığı açıklayan bir yorum ekleyebilirsinizler. Pull request açıklaması gibi bağlam bilgisi olmadan, yakın gelecekte bu kodu anlayıp anlayamayacağınızı kendinize sorun.
07/26/2026
User avatar mt:deepl

Automatically translated
It’s important that the changes are consistent with the rest of the project. Inconsistencies complicate maintenance, and therefore we should avoid them. If there’s an approach to output messages to the user, or report errors, we should stick to that. If the author disagrees with the project’s standards, suggest them to open an issue where we can discuss them further.
Değişikliklerin projenin geri kalanıyla tutarlı olması önemlidir. Tutarsızlıklar bakım işlerini zorlaştırır, bu nedenle bunlardan kaçınmalıyız. Kullanıcıya mesajlar iletmek veya hataları bildirmek için belirli bir yaklaşım varsa, buna bağlı kaluymalıyız. Yazar, projenin standartlarına katılmıyorsa, konuyu daha ayrıntılı olarak tartışabileceğimiz bir sorun bildirimi açmasını önerin.
07/26/2026
Browse all component changes