Fix pre-push hook to always call git lfs pre-push when DRS config incomplete #134
+41
−30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The pre-push hook was returning early when
GetRemoteClientfailed, which skipped both DRS preparation andgit lfs pre-push. This broke LFS file transfers when DRS configuration was incomplete (e.g., "push was called before drs config complete").Changes
prepareDrsObjects(): Isolated error-prone logic into a function that returns early on failures without blocking the main push flowgit lfs pre-pushalways executes: Main hook flow now unconditionally callsgit lfs pre-pushafter attempting DRS preparationBehavior
When DRS config is incomplete or operations fail:
Users can now push LFS files regardless of DRS configuration state. DRS issues are surfaced as warnings to stderr and logs, but don't block Git operations.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.