Skip to content

[CI] Fix the Windows 6.0 check name#2941

Merged
FranzBusch merged 1 commit into
mainfrom
fb-gha-windows-naming
Oct 23, 2024
Merged

[CI] Fix the Windows 6.0 check name#2941
FranzBusch merged 1 commit into
mainfrom
fb-gha-windows-naming

Conversation

@FranzBusch
Copy link
Copy Markdown
Member

Motivation

Currently, the Windows 6.0 check name includes the matrix properties.

Modification

This PR makes it dynamic with the swift version again.

Result

Aligned CI check names across platforms.

@FranzBusch FranzBusch force-pushed the fb-gha-windows-naming branch 6 times, most recently from 4874873 to 4aae502 Compare October 23, 2024 08:08
@FranzBusch FranzBusch added the semver/none No version bump required. label Oct 23, 2024
@FranzBusch FranzBusch marked this pull request as ready for review October 23, 2024 08:22
@FranzBusch FranzBusch enabled auto-merge (squash) October 23, 2024 08:23
# Motivation

Currently, the Windows 6.0 check name includes the matrix properties.

# Modification

This PR makes it dynamic with the swift version again.

# Result

Aligned CI check names across platforms.
@FranzBusch FranzBusch force-pushed the fb-gha-windows-naming branch from 4aae502 to 43eb1ff Compare October 23, 2024 08:23
- image: swift:6.0-windowsservercore-ltsc2022
swift_version: "6.0"
enabled: ${{ inputs.matrix_windows_6_0_enabled }}
if: ${{ inputs.matrix_windows_6_0_enabled }}
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

These if checks caused the naming problems since those are evaluated before the matrix so if we disabled the check then the names would get bad

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

Labels

semver/none No version bump required.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants