github/penpot
1
0
Fork 0
mirror of https://github.com/penpot/penpot.git synced 2026-10-29 05:50:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

📚 The audit props cover the mutations, not every command

Browse Source 
The guide claimed the three keys for every branch operation. The three metadata
mutations and the three reads carry the generic RPC event alone, which records
who called what and no duration, so the section now says which is which.
This commit is contained in:
Álvaro Tejero Cantero 2026-09-16 20:17:29 +02:00
parent f0d6852394
commit c68833d209
No known key found for this signature in database
1 changed files with 14 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/technical-guide/developer/branching.md
View File

@ -591,14 +591,20 @@ The listing is deliberately not gated. It renders the branch panel, so
refusing it would take the panel away rather than protect it, and its cost
is bounded by the summary cache instead.
Every branch operation attaches `:branch-operation`, `:branch-outcome` and
`:branch-duration-ms` to its own audit event, because the generic RPC event
records who called what and not how long it took, and duration is the number
the first enterprise trial will be asked about. Creation, compare, merge,
update-from-main and materialise attach them through `audited`; a save routed
to a branch's op log attaches them on the `update-file` event, whose props it
replaces. Every outcome carries them, the no-op merge, the idempotent
materialise and both refusal shapes included.
Every mutation on a branch attaches `:branch-operation`, `:branch-outcome`
and `:branch-duration-ms` to its own audit event, because the generic RPC
event records who called what and not how long it took, and duration is the
number the first enterprise trial will be asked about. Creation, compare,
merge, update-from-main and materialise attach them through `audited`; a save
routed to a branch's op log attaches them on the `update-file` event, whose
props it replaces. Every outcome carries them, the no-op merge, the
idempotent materialise and both refusal shapes included.
Three mutations are the exception: `update-file-branch`,
`archive-file-branch` and `delete-file-branch` are single-row metadata
updates that carry only the generic event. The three reads are the same:
the listing, the branch context and the limits are hot paths, and the
listing's own cost is recorded by the summary cache instead.
## RPC API summary