You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the issue
GitHub Actions Questions > Question 014 's answer is not correct
"!Q14 :this code will launch 6 different jobs in parallel using the matrix strategy. Can you use the matrix strategy to parallelize entire workflows"
it should be "YES" not "NO"
beucase :
the provided code will launch 6 different jobs in parallel using the matrix strategy.
Here's how it works:
The matrix contains:
3 version values: 10, 12, and 14
2 os values: ubuntu-latest and windows-latest
This creates
3 × 2 = 6
3×2=6 unique combinations of version and os, and each combination corresponds to a separate job.
thanks..
The text was updated successfully, but these errors were encountered:
Please note that the core maintainer of this repository will not be available for support or any work on this repo for the upcoming months. As a result, new features will not be added during this period. Only additions or updates of new questions or study resources will be accepted.
We encourage you to follow the CONTRIBUTING guide and raise pull requests with fixes for content issues you find. Content pull requests will be reviewed by another maintainer.
Thank you for your understanding and contribution! 🚀
Describe the issue
GitHub Actions Questions > Question 014 's answer is not correct
"!Q14 :this code will launch 6 different jobs in parallel using the matrix strategy. Can you use the matrix strategy to parallelize entire workflows"
it should be "YES" not "NO"
beucase :
the provided code will launch 6 different jobs in parallel using the matrix strategy.
Here's how it works:
The matrix contains:
3 version values: 10, 12, and 14
2 os values: ubuntu-latest and windows-latest
This creates
3 × 2 = 6
3×2=6 unique combinations of version and os, and each combination corresponds to a separate job.
thanks..
The text was updated successfully, but these errors were encountered: