GitHub Actions Reusable Workflow Language Collocations
Practise the standard verbs for building reusable GitHub Actions workflows.
0 / 5 completed
1 / 5
Fill in: 'We ___ a reusable workflow for the common test-and-deploy steps, rather than copy-pasting the same YAML into twenty repos.'
We 'extract a workflow' — the standard, simple collocation for pulling shared CI logic into a reusable file. The other options are less idiomatic here.
2 / 5
Fill in: 'Hardcoding a secret name inside a reusable workflow can ___ calling repos unable to actually pass their own credentials in.'
We say a hardcoded name will 'leave' callers unable to pass credentials — the standard, natural collocation for the resulting rigidity. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ workflow inputs explicitly with types and defaults, rather than a bare string nobody's actually documented.'
We 'declare inputs' — the standard, simple collocation for defining a reusable workflow's parameters. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every caller workflow against the pinned reusable version, rather than referencing a branch nobody's actually locked down.'
We 'check a caller' — the standard, simple collocation for confirming a workflow reference is pinned. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a changelog for the shared workflow on every release, rather than breaking twenty repos with an edit nobody actually announced.'
We 'publish a changelog' — the standard, simple collocation for documenting reusable workflow changes. The other options aren't idiomatic here.