mirror of
https://github.com/penpot/penpot.git
synced 2026-10-30 14:30:37 +00:00
::materialize-file-branch persists a branch's derived state as the file's own data payload, drops the op log, releases the pinned base snapshot, closes any pull request over it and clears the branch marker, so every read and write path takes the ordinary route from then on. That is the preview's exit door: the flag can go off and the engine can be replaced without stranding anybody with an unreadable file. It keys on the branch file rather than the branch metadata, so calling it twice is a reported no-op rather than an error.