We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The following 2 strategy matrix are identical:
matrix: scalaVersion: ["2.13.6", "2.13.7"]
equals
matrix: include: - scalaVersion: "2.13.6" - scalaVersion: "2.13.7"
But only the first one can be parse successfully and generate the proper badge
The second produces multiple jobs in github actions, but as a badge they cannot be identified:
Is this a known limitation?
The text was updated successfully, but these errors were encountered:
The case with "include" is not supported just because I didn't have it in mind :(
Sorry, something went wrong.
Are there any cases when you really want to use second variant with include list instead of the first version?
include
Thanks a lot! In my case I sometimes want to construct an incomplete matrix, e.g.:
matrix: include: - scalaVersion: "2.13.6" experimental: true - scalaVersion: "2.13.7" experimental: true
The argument ${{experimental}} can then affect some workflow behaviour
Then these include should be supported in the app. However, I don't have time for this right now :(
No branches or pull requests
The following 2 strategy matrix are identical:
equals
But only the first one can be parse successfully and generate the proper badge
The second produces multiple jobs in github actions, but as a badge they cannot be identified:
Is this a known limitation?
The text was updated successfully, but these errors were encountered: