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

Translation status

15 Strings
0%
Browse Translate
380 Words
0%
2,564 Characters
0%

Strings status

Strings Words Characters
15 380 2,564
All strings Browse Translate Zen
15 380 2,564
Unfinished strings Browse Translate Zen
15 380 2,564
Strings marked for edit Browse Translate Zen
1 89 593
Strings with any failing checks Browse Translate Zen
1 89 593
Failing check: Markdown syntax 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 fix(kura): run the action-cache eviction cascade without waiting on the backfill (#12182) 7a4204e1c9
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/*/guides/features/registry/continuous-integration.md
Monolingual base language file docs/docs/en/guides/features/registry/continuous-integration.md
Translation file Download docs/docs/pt/guides/features/registry/continuous-integration.md
Last change July 25, 2026, 4:05 p.m.
Last change made by Background commit
Language Portuguese
Language code pt
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 249,463,918
Number of plurals 2
Plural type One/other
Plurals Singular 0, 1
Plural 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, …
Plural formula n > 1
07/25/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 15 380 2,564
Translated 0% 0 0% 0 0% 0
Needs editing 100% 15 100% 380 100% 2,564
Read-only 0% 0 0% 0 0% 0
Failing checks 6% 1 23% 89 23% 593
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 22 changes 0 changes 7 changes 0 changes 18 changes 0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 16 changes 0 changes 4 changes 0 changes 10 changes
JulAugSepOctNovDecJanFebMarAprMayJun

Quick numbers

380
Hosted words
15
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 07/25/2026
User avatar mt:deepl

Automatically translated
Additionally, you will need to find a path of the `Package.resolved`. You can grab the path by running `ls **/Package.resolved`. The path should look something like `App.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved`.
Além disso, terá de encontrar o caminho para o ficheiro `« `» no «Package.resolved`»`. Pode obter o caminho executando o comando `« `ls **/Package.resolved`»`. O caminho deverá ser semelhante a « `App.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved»`.
07/25/2026
User avatar mt:deepl

Automatically translated
Since the registry credentials are stored in a keychain, you need to ensure the keychain can be accessed in the CI environment. Note some CI providers or automation tools like [Fastlane]{1} already create a temporary keychain or provide a built-in way how to create one. However, you can also create one by creating a custom step with the following code:
Uma vez que as credenciais do registo são armazenadas num keychain, é necessário garantir que o keychain pode ser acedido no ambiente de CI. Note-se que alguns fornecedores de CI ou ferramentas de automatização, como o [Fastlane]{1}, já criam um keychain temporário ou disponibilizam uma forma integrada de o criar um. No entanto, também é possível criar um keychain definindo um passo personalizado com o seguinte código:
07/25/2026
User avatar mt:deepl

Automatically translated
Additionally, you need to ensure the `TUIST_TOKEN` environment variable is set. You can create one by following the documentation {1}here{2}.
Além disso, é necessário garantirtem de se certificar de que a variável de ambiente `TUIST_TOKEN` está definida. Pode criá-la seguindo a documentação {1}aqui{2}.
07/25/2026
User avatar mt:deepl

Automatically translated
Clean/cold resolutions are slightly faster with our registry, and you can experience even greater improvements if you persist the resolved dependencies across CI builds. Note that thanks to the registry, the size of the directory that you need to store and restore is much smaller than without the registry, taking significantly less time. To cache dependencies when using the default Xcode package integration, the best way is to specify a custom `clonedSourcePackagesDirPath` when resolving dependencies via `xcodebuild`. This can be done by adding the following to your `Config.swift` file:
As resoluções «limpas»/«a frio» são ligeiramente mais rápidas com o nosso registo, e poderá obter melhorias ainda maiores se persistir as dependências resolvidas nas compilações de CI. Note que, graças ao registo, o tamanho do diretório que precisa de armazenar e restaurar é muito menor do que sem o registo, demorando significativamente menos tempo. Para armazenar as dependências em cache ao utilizar a integração padrão de pacotes do Xcode, a melhor forma é especificar um `clonedSourcePackagesDirPath` personalizado `` ao resolver dependências através de ` `xcodebuild``. Isto pode ser feito adicionando o seguinte ao seu ficheiro `Config.swift`` do ` `` :
07/25/2026
User avatar mt:deepl

Automatically translated
Incremental resolution across environments {#incremental-resolution-across-environments}
Resolução incremental em diferentetodos os ambientes {#incremental-resolution-across-environments}
07/25/2026
User avatar weblate:commit

Changes committed
Changes committed 06/25/2026
User avatar mt:deepl

Automatically translated
For Swift packages and the XcodeProj-based integration, we can use the default `.build` directory located either in the root of the project or in the `Tuist` directory. Make sure the path is correct when setting up your pipeline.
Para pacotes Swift e a integração baseada em XcodeProj, podemos ustilizar o diretório padrão `.build`, localizado na raiz do projeto ou no diretório `Tuist`. Certifique-se de que o caminho está correto ao configurar o seu pipeline.
06/25/2026
User avatar mt:deepl

Automatically translated
Additionally, you will need to find a path of the `Package.resolved`. You can grab the path by running `ls **/Package.resolved`. The path should look something like `App.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved`.
Além disso, terá de encontrar o caminho para o ficheiro ` `Package.resolved``. Pode obter o caminho executando o comando ` `ls **/Package.resolved``. O caminho deverá ser semelhante a `App.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved`.
06/25/2026
User avatar mt:deepl

Automatically translated
Since the registry credentials are stored in a keychain, you need to ensure the keychain can be accessed in the CI environment. Note some CI providers or automation tools like [Fastlane]{1} already create a temporary keychain or provide a built-in way how to create one. However, you can also create one by creating a custom step with the following code:
Uma vez que as credenciais do registo são armazenadas num keychain, é necessário garantir que o keychain pode ser acedido no ambiente de CI. Note-se que alguns fornecedores de CI ou ferramentas de automatização, como o [Fastlane]{1}, já criam um keychain temporário ou fornecedisponibilizam uma forma integrada de o criar um. No entanto, também pode criar um criaé possível criar um keychain definindo um passo personalizado com o seguinte código:
06/25/2026
Browse all translation changes