Practise the standard verbs for configuring GitHub branch protection.
0 / 5 completed
1 / 5
Fill in: 'We ___ branch protection on main so nobody can push directly without going through a reviewed pull request.'
We 'enable protection' — the standard, established GitHub collocation for turning on a branch safety rule. The other options aren't the recognised term here.
2 / 5
Fill in: 'Skipping required status checks can ___ a broken build merged straight into main unnoticed.'
We say skipped checks will 'let' a broken build merge — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ at least one approving review before a pull request can merge into a protected branch.'
We 'require a review' — the standard, established collocation for mandating an approval gate. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ force-pushes to main entirely so history can never be silently rewritten on the primary branch.'
We 'block' an action — the standard, simple collocation for disallowing a specific git operation. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ protection rules periodically to confirm admins haven't quietly bypassed them over time.'
We 'audit' rules — the standard, established collocation for periodically reviewing a security configuration. The other options aren't the recognised term here.