Matrix: how to Cartesian-product the include with the other variables #119723
Replies: 3 comments
-
Update: I finally got this working by copying one of the variables from the
But the fact that |
Beta Was this translation helpful? Give feedback.
-
NB: It's possible the issue only affects workflows that need to have explicit full names -- but any CI check does if it's to be used in a ruleset with other forward-compatible variables. |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
For https://github.com/Pr0methean/zip-next/actions/runs/8696381767, I defined the following matrix:
I expected this to produce 9
build-and-test
jobs, but it only produces 3 (the ones that usenightly
). I got the same results with a dummy-variable workaround to make the variable sets overlap:How do I fix this so that
build-and-test
generates 9 jobs, and the ones that use Rust 1.70 havemsrv
rather than1.70
in their names so that I can include them forward-compatibly as PR required checks in my ruleset?Beta Was this translation helpful? Give feedback.
All reactions