Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 9 additions & 10 deletions .github/actions/uitests/action.yml
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,10 @@ inputs:
description: 'Force updating reference images before running UI tests'
required: false
default: 'false'
compute:
description: 'Generate the Example project with the Compute backend'
required: false
default: 'false'

outputs:
test-result:
Expand All @@ -43,14 +47,6 @@ runs:
install: false
cache: false

- name: Install Tuist
run: |
cd Example
mise trust mise.toml
mise install
tuist version
shell: bash

- name: Set up build environment
run: Scripts/CI/darwin_setup_build.sh
shell: bash
Expand All @@ -67,8 +63,11 @@ runs:
shell: bash
run: |
cd Example
mise exec -- tuist install
mise exec -- tuist generate --no-open
if [[ "${{ inputs.compute }}" == "true" ]]; then
./setup.sh --compute

@augmentcode augmentcode Bot Jul 5, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now that CI generates the Example project via Example/setup.sh, changes to that script (and its associated mise*.toml env files) can affect UI test setup. Consider adding those paths to .github/workflows/uitests.yml on.push.paths so setup regressions will reliably trigger UI tests on main.

Severity: medium

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.

else
./setup.sh
fi

- name: Resolve snapshot reference directory
id: reference
Expand Down
Loading
Loading