Ref-level pull attribution (Strategy B want-parsing) #4
Labels
No labels
Compat/Breaking
demo
hardening
identity
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
needs-verification
notify
ops
packaging
perf
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
process
rbac
research
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
scanning
stage-6e
stage-6f
stage-6g
Status
Abandoned
Status
Blocked
Status
Need More Info
transport
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
qwc-open/tulli#4
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Labels:
enhancement,notify,transportPriority: high (it's the headline "you pulled evil@abc123" promise)
Parse the upload-pack negotiation "wants" so
access_events.ref/commit_shaare populated; notify becomes ref-precise, not just repo-precise. Also unlocks band-2 sideband "why this ref is hidden" messages to the git client.upload-pack(Strategy B) instead of pure CGI handoff, or parse the POST body to capture wantsaccess_events.ref/commit_sha