Tuist 4.26.0 adds GitHub integration, letting teams connect remote projects to a GitHub repository via a CLI command and the Tuist GitHub app, enabling automatic posting of test results and one-click previews. It also introduces a new command, tuist inspect implicit-imports, which uses static analysis to catch implicit dependencies in Xcode projects that often cause build slowness and instability. Smaller fixes address outdated dependency detection and a false-positive bug with static dependency side effects. The team also teases upcoming Tuist Workflows, a Swift-based CI automation approach.
Table of contents
Meeting developers where they are: GitHub integrationImplicit dependencies: Developers' worst nightmareOther changesWhat's nextQuestions this post answers
How do I detect implicit dependencies in my Xcode project using Tuist?
Run the command tuist inspect implicit-imports in a Tuist project. It uses static code analysis to find modules that implicitly depend on others (for example, a file adding 'import Network' without declaring it explicitly), and it fails the command if implicit imports are detected, though it won't catch every instance. Developers hunting build-time slowdowns can follow tooling updates like this on daily.dev.
How do I connect my Tuist project to a GitHub repository?
Use the command 'tuist project update tuist/tuist --repository-url https://github.com/tuist/tuist' to link a remote Tuist project to a GitHub repo, then install the Tuist GitHub app in that repository. Once connected, Tuist can automatically post test results and one-click previews on pull requests. Teams wiring CI feedback into GitHub can track integrations like this via daily.dev.