You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enhance LFS error handling and logging in fetch and push operations (#8)
* Add error handling for LFS fetch and push operations with logging
* Enhance LFS handling and review logging in absorb process
* Fix LFS fetch references in absorb and publish methods
Copy file name to clipboardExpand all lines: SPEC.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,7 +150,7 @@ pubgate supports repositories that use Git LFS. LFS support is auto-detected via
150
150
151
151
**How it works:** LFS-tracked files are stored as pointer files in git. pubgate reads and writes these pointers as-is; they pass through the snapshot, stage, and publish pipelines without modification. When files are staged with `git add`, git's clean/smudge filters handle the LFS encoding automatically via `.gitattributes`.
152
152
153
-
**LFS object transfer:** pubgate runs `git lfs fetch`during command startups (absorb, publish) to ensure LFS objects are locally cached, and `git lfs push` after pushing branches to transfer LFS objects to the destination remote's LFS server.
153
+
**LFS object transfer:** pubgate runs `git lfs fetch`before file operations that need blob content (absorb, publish), skipping the fetch when there is no work to do (e.g. already up to date) or during `--dry-run`. After pushing branches, `git lfs push` transfers LFS objects to the destination remote's LFS server.
154
154
155
155
**Limitations:**
156
156
-**LFS files are treated as binary**: they are never merged during `absorb` (copied/overwritten instead) and never scrubbed for `BEGIN-INTERNAL`/`END-INTERNAL` markers during `stage`. Do not place internal markers inside LFS-tracked files; use ignore patterns in `pubgate.toml` to exclude sensitive LFS files from publication.
0 commit comments