The shell guard compares git long flags exactly, but git accepts any unambiguous prefix of a long option, so the no-verify flag of commit and push, and the with-lease and if-includes force flags of push, each spelled a few letters short, run as the full flag and are allowed. Found by review-guard finding 4 (pre-existing).

The shell guard compares git long flags exactly, but git accepts any unambiguous prefix of a long option, so the no-verify flag of commit and push, and the with-lease and if-includes force flags of push, each spelled a few letters short, run as the full flag and are allowed. Found by review-guard finding 4 (pre-existing).

Grounds

• pursued: every prefix git resolves to a blocked push or commit option blocks, and prefixes git resolves to another option stay allowed; an allow of a unique prefix of a blocked option, or a block of a prefix of a different option, would show it wrong