Skip to main content

clone_refusal

git_policy_cli::worktree::worktree_snapshot_source

Function clone_refusal 

Source 
pub fn clone_refusal(
    identity: &WorktreeIdentity,
    plan: &AddPlan,
) -> Option<String>
Expand description

What: The cheap reasons the clone rung cannot serve a planned add: either side is on a filesystem that never clones, or the two are not in one clone domain (one btrfs filesystem, or one device elsewhere). Why: A clone crosses subvolumes of one btrfs filesystem and nothing else; an overlay or XFS is one device.

In TS you’d write (pseudocode):

function cloneRefusal(identity: WorktreeIdentity, plan: AddPlan): string | undefined;