Struct ReplayRequest 

pub struct ReplayRequest<'a> {

    pub context: &'a GitContext,
    pub shadow: &'a Path,
    pub object_directory: &'a Path,
    pub worktree_root: &'a Path,
    pub git_dir: &'a Path,
    pub transaction_directory: &'a Path,
    pub replay: u64,
    pub base: Option<&'a str>,
    pub empty_tree: &'a str,
    pub current: &'a str,
    pub prepared: &'a str,
    pub signing_key: Option<&'a str>,
    pub global_arguments: &'a [String],
}

What: One replay’s inputs: the Git context and directories, the transaction, the commit IDs, and the signing options. Why: A struct keeps the call site short; every field is named once.

In TS you’d write (pseudocode):

type ReplayRequest = { gitPath; shadowPath; objectDirectory; cwd; gitDir; directory; replay; base; emptyTree; current; prepared; signingKey; globalArgs };

Fields

context: &'a GitContext

Real Git executable and the variables every child receives.

shadow: &'a Path

Shadow repository, as --git-dir.

object_directory: &'a Path

Shadow object store, whose alternates reach the real objects.

worktree_root: &'a Path

Worktree root, where Git reports conflicted paths from.

git_dir: &'a Path

Git directory of the owning worktree, holding the capture store.

transaction_directory: &'a Path

This transaction’s directory, holding captured.json.

replay: u64

Replay number, naming the private files.

base: Option<&'a str>

Preparation base commit; None for an unborn branch.

empty_tree: &'a str

Empty tree of the repository’s object format, for an unborn base.

current: &'a str

Target that won.

prepared: &'a str

Prepared commit.

signing_key: Option<&'a str>

Key the invocation passed to -S; None signs with the configured key.

global_arguments: &'a [String]

The caller’s kept global options, which may configure signing.