Practise the standard verbs for configuring GitHub Actions matrix builds.
0 / 5 completed
1 / 5
Fill in: 'We ___ a build matrix across node versions and operating systems so a regression on one combination doesn't slip through unnoticed.'
We 'define a matrix' — the standard, established GitHub Actions collocation for declaring a combination of build variables. The other options aren't the recognised term here.
2 / 5
Fill in: 'Testing on a single node version instead of a matrix can ___ a compatibility bug reaching users on an older runtime.'
We say a single-version test will 'leave' a compatibility bug undetected — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ fail-fast to false on the matrix so one failing combination doesn't cancel every other job before it finishes.'
We 'set' a flag — the standard, simple collocation for configuring a workflow behaviour option. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ a specific combination from the matrix using an exclude rule when a known incompatibility makes that pairing pointless to test.'
We 'exclude' a combination — the standard, established matrix collocation for removing an unwanted pairing from the generated jobs. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ matrix job results in a single summary check so a PR shows one clear pass/fail instead of a dozen individual statuses.'
We 'aggregate' results — the standard, established collocation for combining multiple job outcomes into one status. The other options aren't the recognised term here.