GitHub delivery handoff

Plan and ship to GitHub with a reviewed pull request

Turn an accepted Work Plan into an ownership-scoped branch, commit, and pull request. Codelit previews the exact repository state before it writes and preserves a receipt for the handoff.

Start with feature delivery Inspect the public example

Accepted Work Plan

Pinned repository state

Owned branch and commit

Pull request and receipt

Real adapter behavior

What Codelit actually does.

A review branch, one atomic handoff commit, and an open pull request tied to the accepted source revision.

Pins the destination

Confirms the selected repository, writable permission, default branch, base commit, and Codelit handoff branch before approval.

Protects existing code

Refuses file collisions and branches without a matching Codelit ownership manifest. Only the reviewed pack and ownership receipt are managed.

Writes one reviewable change

Creates or advances the owned branch with one atomic commit, then opens or updates its pull request.

Recovers without duplicate work

Uses a handoff marker and durable receipt so a retry can recognize a commit that already completed.

Stops before an unsafe write

The repository is missing or the connected account cannot write.
The base branch or handoff branch changed after preview.
A reviewed path would overwrite a file Codelit does not own.
The handoff branch exists without this Project's ownership manifest.

Proof after the handoff

Pinned source and Delivery Graph fingerprints
Commit SHA and pull request reference
Per-node synchronization status
Exact completion time and provider response

Continuity after handoff

Provider drift becomes a decision, not a surprise.

Later checks distinguish a merged pull request from a closed, missing, or changed branch. A base-branch change only raises drift when it touches a managed handoff path.

Common questions

Can Codelit write to GitHub automatically?

Codelit prepares the handoff automatically, but the external write remains a reviewed action. You see the exact destination and planned changes before approving it.

What happens if GitHub changes after the preview?

Codelit stops the stale handoff and asks for a fresh preview. It does not silently overwrite provider-side changes.

What proof remains after the handoff?

A review branch, one atomic handoff commit, and an open pull request tied to the accepted source revision.

Plan the work before the provider write.

Start free, review the ladder, then connect GitHub when the handoff is ready.

Start this delivery