Skip to content

Where people and agents ship software together. The open-source git platform for the whole job: issues, agents, checks and deploys to the edge.

Commit

The landing page says what the demo shows: Coordination named only pull requests flagged to each other, though agents also claim issues, show live as sessions, are told of overlapping files before a pull request exists, and get a merge-queue break routed back to the session that caused it; it now says so and links Sessions, claims and overlaps. Ship safely says checks run free on your own runners, including your computer while the desktop app is open (a point replaces Workflows from .g1t/workflows). Run it says a new app can start from one sentence on Home: one click makes the repository, starts your coding agent and puts the first version live (Ask's new-repository card, #53). Checked against the sessions, merge-queue, self-hosted-runners, desktop and ask guides; apps/web typecheck.

G1t-Session:
ses_01m4ysye20ecnrq04gbbm7nzk1
syntaqxcommitted Parent216cb23Browse files
1 file+16−90/1 viewed
+16−9
521521 title="Main only moves to what passed"
522522 art={<QueueArt className="w-full" />}
523523 points={[
524− "Checks in a clean sandbox, or on your own runners",
525− "Workflows from .g1t/workflows",
524+ "Checks in a clean sandbox, or free on your own runners",
525+ "Your computer as a runner, with the desktop app",
526526 "A merge queue that tests changes together",
527527 "Conflicts found on every push, before a merge",
528528 "Catch up with main in seconds",
530530 ]}
531531 more={["The merge queue", `${DOCS}/guides/merge-queue/`]}
532532 >
533− Required checks run on g1t&apos;s runners or your own. The queue
533+ Required checks run on g1t&apos;s runners, or free on your own: a
534+ server, or your computer while the desktop app is open. The queue
534535 tests each change together with what lands ahead of it; one that
535536 breaks goes back to its author with what failed, and main never sees
536537 it.
563564 "A live preview for every pull request",
564565 "Production on every merge to main",
565566 "Custom domains, with certificates",
567+ "A new app from one sentence on Home",
566568 ]}
567569 more={["Deployments", `${DOCS}/guides/deployments/`]}
568570 >
569571 Turn on deployments and every pull request gets its own address on
570572 g1t.page; merging ships production. Reviewers click through a
571573 change instead of reading a diff. An app nobody visits runs nothing
572− and costs nothing.
574+ and costs nothing. Or start from Home: ask for something new, and one
575+ click makes its repository, starts your coding agent on it and puts
576+ the first version live.
573577 </Pillar>
574578 </div>
575579 </section>
728732 Many agents, no collisions
729733 </h3>
730734 <p className="mt-3 text-sm leading-6 text-muted">
731− Run as many coding agents as you like. Each change is a pull
732− request, pull requests that touch the same files are flagged to
733− each other, conflicts are found on every push, and the merge queue
734− tests changes together with what lands ahead of them. Five agents
735+ Run as many coding agents as you like. Each claims the issue it
736+ takes, and every session shows live as it works, so everyone sees
737+ who is on what. Two that start changing the same files are told
738+ while they work, before either opens a pull request. The merge
739+ queue tests changes together with what lands ahead of them, and
740+ one that breaks another goes back to the session that caused it,
741+ with the change it breaks and the check that failed. Five agents
735742 can open pull requests the same afternoon and main still only
736743 moves to what passed.
737744 </p>
738− <More to={`${DOCS}/guides/merge-queue/`}>The merge queue</More>
745+ <More to={`${DOCS}/guides/sessions/`}>Sessions, claims and overlaps</More>
739746 </div>
740747 </div>
741748 </section>

Comments

Sign in to comment.