Skip the Source-Only Refspec Mapping for a Delete Push in the Write Guard #3314

Problem

The write guard's source-only refspec mapping (added for #3048 and #2943's persisted push config item) reads a --delete push's refspecs as if git mapped them. Git does not: it turns each --delete word into :<name> before any remote.<name>.push or push.default=upstream mapping is reached, so only the named branch is deleted.

The guard therefore reads a routine branch cleanup as deleting the branch the mapping names. This is an over-denial, found by the local review on the pull request closing #3048, and per that lane's rule it is filed rather than narrowed in the same pull request.

Reproduction (constructed repository)

1. A checkout whose origin's develop carries a deletion or pull_request rule.
2. git config push.default upstream, on a branch feature/example whose branch.feature/example.merge is refs/heads/develop (the shape git worktree add -b feature/example <path> origin/develop leaves).
3. Classify git push origin --delete feature/example in that checkout.

The guard denies it as a write to develop. A real push there deletes only feature/example. A remote.origin.push of refs/heads/feature/example:refs/heads/develop gives the same denial.

Possible Direction

Skip the source-only mapping for a push carrying --delete (or -d, in any spelling _push_targets already reads as a delete), since git never maps it.

🤖 Generated with Claude Code