Module lfs_interactive 

The Git LFS step before a push the caller typed: pre-check, plan and upload with the caller’s streams. What: The Git LFS step before a push the caller typed: the pre-check, the plan and the upload, with the caller’s streams. Why: The parent owns the whole step, so a refusal, a plan that cannot be worked out and a failed upload are all explained by the process that saw them, and the push is not started after any of them. The configuration the plan reads comes from the snapshot the wrapper already took when it planned the invocation, so a push whose repository is known costs no Git start for it; without a snapshot one config --get-regexp start reads it.

In TS you’d write (pseudocode):

const stop = await uploadBeforePush({ prefix, region, realGit, environment, overlay, settings }); if (stop !== undefined) return stop;

Structs

InteractiveUpload

What the step needs from the invocation.

Functions

upload_first

What: Run the step; the status to stop with when the push must not start, or nothing when it may. Why: A missing git-lfs, a plan that cannot be worked out and a failed upload each end the push before it starts.