Consolidate mise configuration at repository root#944
Conversation
🤖 Augment PR SummarySummary: Moves the Compute mise environment config to the repository root and removes the duplicated Example-level default mise config. 🤖 Was this summary useful? React with 👍 or 👎 |
|
|
||
| ```shell | ||
| mise trust mise.compute.toml | ||
| mise trust ../mise.compute.toml |
There was a problem hiding this comment.
The manual Compute instructions only mise trust ../mise.compute.toml, but mise --env compute … will typically still load the base ../mise.toml as well. If someone follows just this section, they may still hit an untrusted-config prompt for mise.toml.
Severity: low
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #944 +/- ##
==========================================
- Coverage 26.35% 26.35% -0.01%
==========================================
Files 723 723
Lines 51232 51232
==========================================
- Hits 13504 13500 -4
- Misses 37728 37732 +4 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Summary
Example/to the repository rootExample/Why
The root and Example default configurations duplicated the same Tuist version and AttributeGraph environment. Keeping the default and Compute configurations together at the repository root provides one source of truth while still allowing commands run from
Example/to inherit the appropriate mise environment.Impact
The recommended
Example/setup.shworkflow remains unchanged for users. Both default AttributeGraph generation and--computegeneration now resolve their mise configuration from the repository root.Validation
bash -n Example/setup.shgit diff --check