Hive Hive
Sign in
Projects
Domains
Forage
Specs
Drops

Add GitHub workflow job that builds Tuist

GitHub issue · Open

Metadata
Source
tuist/tuist #7632
Updated
Jun 11, 2026
Details

Why is this needed?

There was a bug in the sandboxing implementation which was not caught in PR because the GitHub workflow jobs use a published version of Tuist to generate.

I’m not sure how often that kind of thing happens, but we could protect against it with a GitHub workflow job that:

  1. Uses the mise version of Tuist to generate the Tuist project
  2. Builds Tuist
  3. Uses the built version of Tuist to generate the Tuist project
  4. Builds Tuist

This should catch that kind of regression.

Steps to address the need

  1. Add a new job to .github/workflows/tuist.yml that performs the above steps.
Comments
F
fortmarek Jun 4, 2025

I’m not sure how often that kind of thing happens, but we could protect against it with a GitHub workflow job that:

I’m actually somewhat surprised the acceptance tests were not able to catch this issue as we do run the flow end-to-end and I would have expected the sandbox to raise an issue in that scenario, too. We can consider doing what you’re suggesting, though