Expand description
Refspec resolution for the LFS lock APIs.
LFS lock create/delete/list endpoints all carry a ref.name field
that the server can use to enforce per-branch lock scoping. Upstream
resolves this once per command and ships it on every request: the
tracked upstream branch (from branch.<current>.merge) takes
precedence, falling back to the current branch’s full ref. A
detached HEAD has no resolvable refspec, in which case the field
is omitted from the request.
Functions§
- current_
refspec - Resolve the refspec to send with lock-API requests, or
Noneif the working tree is on a detached HEAD.