> ## Documentation Index
> Fetch the complete documentation index at: https://gump.build/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Apply the Result

> When a run completes successfully, the result lives in an isolated Git worktree.

# Apply the Result

When a run completes successfully, the result lives in an isolated Git worktree. Your main branch is untouched. To merge the result into your working branch:

```bash theme={null}
gump apply
```

This does a `git merge` from the run's branch (`gump/run-<uuid>`) into your current branch. Conflicts are handled by Git — resolve them with your usual tools.

Gump adds a trailer to the merge commit for traceability:

```
Gump-Run: a1b2c3d4-e5f6-7890-abcd-ef1234567890
```

You can always trace back from a commit to the run that produced it.

## What if I want to inspect first?

After a run, before applying, you can:

**Check the report:**

```bash theme={null}
gump report
```

**Look at the diff:**

```bash theme={null}
cd .gump/worktrees/run-<uuid>
git diff main
```

**Browse the generated code** in the worktree directory. It's a normal Git repo.

## Apply a specific run

If you've run multiple workflows, specify which one to apply:

```bash theme={null}
gump apply --run <uuid>
```

## Clean up old runs

Worktrees and run artifacts accumulate. Clean them up:

```bash theme={null}
# Keep only the last 5 runs
gump gc --keep-last 5
```

This removes old worktrees, branches, and ledger files. Runs that haven't been applied will prompt for confirmation.