Git hosting with Actions built in

Repositories, pull requests, rulesets, and releases — and, at launch, workflows that run on hosted Linux runners and gate the merge.

Try the preview See the platform

acme / checkout-apiPrivateSearch or jump to…/

CodeIssues 14Pull requests 3ActionsInsightsSecuritySettings

main 5 branches · 8 tagsCode

ari Make webhook retries idempotent (#112)8ad1e773 hours ago· 214 commits

.github/workflowsci: cache bun install2 days ago

docsdocument retry headers5 days ago

srcMake webhook retries idempotent3 hours ago

testcover duplicate deliveries3 hours ago

package.jsonbump zod to 4.42 days ago

README.mddocs: local setup5 days ago

tsconfig.jsonenable strict null checks3 weeks ago

Open 3Closed 41New pull request

Retry failed payouts with backoff#133 · payouts/backoff · samauto-merge on

Log idempotency key collisions#132 · webhooks/key-log · ari✓ 3 checks passed

Document the release flow#126 · docs/release · samreview requested

Merged this week

Make webhook retries idempotent#112ari · 3 hours ago

Expose idempotency keys in the API#129lena · yesterday

Bound refund handler retries#127sam · 2 days ago

Cache bun install in CI#124ari · 2 days ago

About

Payments API for the Acme storefront. Reviewed, checked, and released from this repository.

typescriptapipayments

Releases 8

v1.9.3Latest

1 hour ago

Checks on main

buildtestlint

reported by ci · 8ad1e77

Languages

TypeScript 86% · SQL 9% · Shell 5%

Works with what you already havegit push.github/workflowscheck runs from any CIREST APIgbb CLI

01Review and merge

Review with the proof attached. Rulesets decide how main changes.

Diffs, review threads, approvals, and required checks on every pull request, with rulesets that hold the line on main.

Make webhook retries idempotent #112

Mergedari merged 3 commits into main from webhooks/idempotent-retries

src/webhooks/retry.ts+4 −1

40 export async function deliver(event: WebhookEvent, store: DeliveryStore) {

41 const key = event.deliveryId;

42- await send(event);

42+ if (await store.seen(key)) {

43+ return { status: "duplicate" };

44+ }

45+ await send(event, { idempotencyKey: key });

46 log.debug(`delivered ${key}`);

sam reviewed 5 hours ago Resolved

Cover the timeout path here too — a retry after a timed-out first attempt was the duplicate we saw in production.

test/webhooks/retry.test.ts+6 −0viewed

Merged· 8ad1e77 on main

All 3 required checks passed· build, test, lint · reported by ci.acme.internal

Review approved· sam

Ruleset · Protect mainActiveTarget: protected branches · enforcement active

Require pull request approvals

Required approvals: 1 · owner approval required

Restrict file paths

secrets/** · *.pem

Maximum file size

5 MB per file

Required deployments

staging must succeed before merging

Commit metadata rules

author_email ends_with @acme.com

Bypass list

team platform-maintainers · until 2027-03-31

Bypass: team platform-maintainers · last changed by ari · 2 minutes ago

Required checks

Actions runs and check runs from any other CI report to the pull request; rulesets make them required.

Required reviews

Approvals, stale-approval dismissal, and resolved conversations before merge, plus force-push and deletion protection.

Auto-merge

Auto-merge lands the pull request the moment its required checks pass.

02Actions · planned for launch

CI that lives next to the code. Hosted runners included.

Workflows in .github/workflows run on hosted Linux runners when you push, open a pull request, or dispatch by hand — and every run reports to the pull request as a check your rulesets can require.

Workflow files

Jobs, steps, needs, matrices, and expressions in .github/workflows, run on push, pull request, or manual dispatch.

Hosted runners

Linux x64 runners with minutes included in every plan, plus logs, artifacts, and caches for every run.

Secrets and environments

Encrypted secrets, environments that wait for approval, and OIDC tokens for AWS instead of stored keys.

03The platform

Everything you'd expect. Nothing you have to bolt on.

One repository, one permission model, one audit trail — from the first commit to the release that ships.

04Organizations & security

Built for teams that answer to someone.

Repository and release actions — from the web, git, or the API — are authorized by capability and recorded, with organization roles and policy controls on top.

Organizations and roles

Organizations, teams, and owner, admin, member, and billing roles.

Sign-in

Two-factor, passkeys, SSH keys, and scoped tokens.

On the record

Capability-based permissions with audit events.

05Command line and migration

A native CLI that speaks the whole platform.

One Rust binary, no runtime to install. Signed builds for macOS, Linux, and Windows — with checksums, SBOMs, and provenance you can verify before you trust it.

One command creates the repository and adds a gbb remote beside origin; a plain git push mirrors your branches and tags without touching any upstream. Keep both remotes in parallel and cut over when the team is ready.

Migrate a repository Get the CLI

gbb — zshgbb 0.8.0 · aarch64-apple-darwin

$ gbb repo create acme/checkout-api --private --source . --push

created repository acme/checkout-api at https://gbb.example/acme/checkout-api

added remote gbb -> https://gbb.example/acme/checkout-api; origin was not changed

$ git push gbb webhooks/idempotent-retries

* [new branch] webhooks/idempotent-retries -> webhooks/idempotent-retries

$ gbb pr create --title "Make webhook retries idempotent" --head webhooks/idempotent-retries

{ "pullRequest": { "number": 112, "state": "open", … } }

$ gbb check watch --ref webhooks/idempotent-retries

{ "checks": [ build success, test success, lint success ], … }

$ gbb pr merge --squash 112

{ "message": "Pull request merged.", "pullRequest": { "number": 112, "state": "merged", … } }

Long JSON responses are trimmed to their first fields; the CLI prints them in full.

06GBB Code

A free AI editor that ships to your repositories. Your agents, your accounts.

Threads, agents, and a real editor in one desktop app. When the work is ready, Create PR opens it here, on the platform that reviews and merges it.

Bring your own agentCodexClaude CodeGrokon your own accounts

Download GBB Code

ThreadsFilesChangesProjectsMake webhook retries idempotentcheckout-apiClaude Code · nowRequire the migration check on maincheckout-apiCodex · 18mDocument the retry policydocsCodex · 1hBump the payments SDKcheckout-apiGrok · 2hFix rounding in the cart totalstorefrontClaude Code · 3hExplain the checkout flowstorefrontCodex · 5hSettings

ConversationFocus AI

Timed-out webhook retries resend events the store already delivered. Make retries idempotent and add a test.

Thought for 9s

Read src/webhooks/retry.ts

Edited src/webhooks/retry.ts+18 −4

Edited src/webhooks/store.ts+9 −1

Added test/retry.test.ts+15

Ran bun test143 passed

Retries now send the delivery's idempotency key, and the store skips a delivery it has already sent. The new test times out a delivery, retries it, and checks the event goes out once.

3 files changed+42 −5

retry.tssrc/webhooks+18 −4

store.tssrc/webhooks+9 −1

retry.test.tstest+15

checkout-api-webhook-retryclaude/webhook-retryNo changes+42 −5Create PR#112

Ask for a follow-up

Workspace writeClaude Code

retry.tsstore.tsretry.test.tsSaveSplit

src › webhooks › retry.ts

1import { deliveries } from "./store";

2import type { Delivery } from "./types";

4export async function retryDelivery(delivery: Delivery) {

5 const key = delivery.idempotencyKey;

6 if (await deliveries.wasSent(key)) return;

7 const response = await send(delivery, {

8 headers: { "Idempotency-Key": key },

9 timeoutMs: 10_000,

10 });

11 if (response.ok) await deliveries.markSent(key);

12 return response;

13}

15export function backoff(attempt: number) {

16 return Math.min(30_000, 500 * 2 ** attempt);

17}

Threads by project

Each conversation is a thread under its project, with its branch and agent on the card, so running work stays in view.

Your agents, your accounts

Codex, Claude Code, or Grok on the plans you already pay for. Provider credentials stay on the host that runs the agent.

A worktree per task

A task that may write gets its own worktree and branch, so what it changed is one diff you can read or drop.

A real editor beside it

Monaco sits next to the conversation: open what the agent touched, read the diff, edit, and save.

Three access levels

Read only, workspace write, or full access, picked per thread. None of them is an OS sandbox.

Create PR, then review here

The branch bar opens the pull request on the platform, where review, required checks, and rulesets take over.

07Planned launch pricing

Start free. Pay for what your team needs.

Free personal accounts and organizations of any size. Team adds organization-wide management for $4 per person a month; optional hosted resources are billed separately.

Planned for launch

Free

For individuals and organizations of any size

$0 USD

Unlimited members and collaborators

Try the preview

Planned for launch

Team

Shared workflows and organization-wide management

$4 USD / human / month

Per human user / month; no minimum team size

Ask about Team

Later release

Enterprise

Enterprise identity, governance and support

$21 USD / human / month

Per human user / month; not available at first launch

Discuss Enterprise

Planned launch pricing, not a claim of current availability. Included usage and paid services remain subject to release qualification. Preview limits may differ; no paid usage starts without an explicit price and spending authorization.

Free organizations include a planned Actions allowance. Enterprise is a later release. See planned allowances and usage rates.

08Questions

The short answers.

Can we bring our existing workflows?

Workflows in .github/workflows run here when they use push, pull_request, or workflow_dispatch triggers, Linux jobs, run steps, matrices, and JavaScript actions kept in the same repository. Actions from other repositories, Docker and composite actions, scheduled triggers, job and service containers, and Windows or macOS runners are not supported yet.

How do we move a repository?

gbb repo create --private --source . --remote gbb adds a second remote beside origin, and git push gbb --all mirrors every branch. Keep both until you are ready to cut over.

Can an organization stay on Free?

Yes. The planned Free plan covers personal accounts and organizations with unlimited members and collaborators. Creating an organization or inviting a teammate is not an upgrade trigger.

Do we need the desktop app?

No. Everything here works from the browser, plain git, the REST API, and the gbb CLI. GBB Code, the free desktop editor, adds threads with your own agents and opens pull requests here — and agents never take a seat.

Bring your repositories over

Create an organization, push a repository, and let its workflows run — or move one over beside your current host.

Try the preview Migrate a repository