Skip to content

Conversation

@jakepetroules
Copy link
Contributor

@jakepetroules jakepetroules commented Dec 13, 2025

The previous method of excluding matrix entries results in complaints annotating the action run (even though the matrix produces the correct entries and works), but this noise gets in the way of real errors and may be bothersome.

Use a new technique (which amusingly is even simpler) to skip the whole matrix when the enabled flag is off for a group of builds.

@jakepetroules jakepetroules force-pushed the eng/PR-fix-annotations branch 10 times, most recently from 8425c7c to f04a9c2 Compare December 13, 2025 07:40
The previous method of excluding matrix entries results in complaints annotating the action run (even though the matrix produces the correct entries and _works_), but this noise gets in the way of real errors and may be bothersome.

Use a new technique (which amusingly is even simpler) to skip the whole matrix when the enabled flag is off for a group of builds.
@jakepetroules jakepetroules changed the title test Fix error annotations Dec 13, 2025
android-sdk-build:
name: Swift SDK for Android Build (${{ matrix.swift_version }} - ${{ matrix.os_version }} - NDK ${{ matrix.ndk_version }})
runs-on: ubuntu-latest
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This looks useless but interestingly making runs-on dependent on a matrix entry rather than a string literal prevents it from creating a job with an empty configuration when the matrix is empty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant