01 / DENGEL GIT

Agents propose.
People land.

Dengel Git is a Git server built in Rust. Developers use the Git they already know. Agents can read exact revisions without a checkout and push candidates that leave main untouched.

01 / REPOSITORYILLUSTRATIVE

acme / storefront

PRIVATE
mainCanonical branch
42df9a1
Retry failed checkoutsPushed to a candidate ref
a91f8c2
The candidate is stored. The team’s main branch stays at 42df9a1.

01 HOW IT WORKS

One repo. A clear path to main.

A candidate is a commit you can inspect and verify while the shared branch stays where it is.

  1. 01 / WORK

    Clone and fetch.

    Copy the HTTPS clone URL from Code and use your existing Git client and editor. In the web panel, browse files and history or switch refs.

  2. 02 / PROPOSE

    Push a candidate.

    Push to a candidate ref and open a proposal in the web panel. The proposal identifies the candidate commit and its base on main. Reviewers can see what it is for and which files changed.

  3. 03 / LAND

    Review before main moves.

    When required checks pass, the panel offers an authorized reviewer a separate merge confirmation. If main moved in the meantime, Dengel refuses the stale proposal.

02 WHY WE BUILT THE SERVER IN RUST

A push can finish before review starts.

We wanted the Git server itself to enforce which writes count. Incoming objects are checked in a temporary area before they enter the repository. A valid push stores the candidate, so checks and review can happen after the Git connection closes.

Updating main is a separate server operation. Dengel checks that the branch still points to the expected commit before moving it. That matters when two agents start from the same base and one change lands first.

SAME GIT PROTOCOL

Keep your tools.

We built a clean-room Git server in Rust from Git’s published formats and protocol. Its Rust receive path validates the objects sent in a push and can reject malformed input before it reaches the object store. Standard Git clients still clone, fetch, and push over HTTPS.

For a developer, the new step is review. For an agent, the candidate ref gives it somewhere to put work without moving the team’s shared branch.

03 REPOSITORY ACCESS FOR AGENTS

Read one file at one commit.

With repository read access, an agent or CI job can use authenticated JSON queries for files, trees, history, changed paths, and diffs. A one-file question does not require a clone.

ILLUSTRATIVE REQUEST · REPOSITORY AUTHENTICATION REQUIREDGET /{repo}.git/query/read-file?rev={full-commit-id}&path=src/checkout.rs

Pin the read to the full commit ID so a branch update cannot change the answer.

PUSH A CANDIDATE FROM YOUR CHECKOUTgit push origin HEAD:refs/heads/candidate/retry-checkout

With a repository push credential, an agent can submit code to that ref. An authorized reviewer uses the web panel to open the proposal, inspect checks, and decide whether to merge it.

NEXT IN THE FACTORY

See how changes get verified.

Explore Dengel Guard