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.

g1t.sh

Commit

The runner guide no longer says the merge queue runs tests on your runners, the pull request guide says working copy, and llms.txt lists the build-and-ship guide (#52). Since b5c43d31 the queue starts no jobs of its own (services/work/src/queue.rs queue_build returns none), so g1t's work on self-hosted runners is its pull request checks and merge checks. A pull request's own copy is a working copy, as Forks and working copies calls it. Checked: queue_build in services/work/src/queue.rs, concepts/forks.md's headings.

G1t-Session:
ses_01m4ynr1peevvs8zwaqakycv2e
syntaqxcommitted Parent2a5bee5Browse files
3 files+5−50/3 viewed
+2−2
599599 git push origin my-branch
600600 ```
601601
602− For a pull request in its own fork, clone the fork and pull `main` into
602+ For a pull request in its own [working copy](/concepts/forks/#working-copies-for-pull-requests), clone the working copy and pull `main` into
603603 it instead:
604604
605605 ```sh
633633 is behind; otherwise it shows it when the repository suggests updating
634634 branches (on by default), and merging brings the branch up to date by
635635 itself. Whoever can push to the pull request (whoever opened it, for one
636−in its own fork; anyone with the Write [role](/guides/access-and-roles/)
636+in its own working copy; anyone with the Write [role](/guides/access-and-roles/)
637637 or higher, for a branch of the repository; whoever can push to the fork,
638638 for a branch of a fork) can update it, two ways:
639639
+2−3
11 ---
22 title: Self-hosted runners
3−description: Run your workflow jobs, and if you choose g1t's checks and merge queue, on your own machines. Their time costs nothing.
3+description: Run your workflow jobs, and if you choose g1t's own checks, on your own machines. Their time costs nothing.
44 ---
55
66 import { TabItem, Tabs } from '@astrojs/starlight/components';
721721 ## g1t's work on your runners
722722
723723 **Runners → Where work runs** can send g1t's own work to your runners
724−too: the checks g1t runs on pull requests, merge checks and the merge
725−queue's test runs. Switch on **Run g1t's work on self-hosted runners** and
724+too: the checks g1t runs on pull requests and merge checks. Switch on **Run g1t's work on self-hosted runners** and
726725 give the labels a runner needs to take it (`self-hosted` is always one).
727726
728727 - The work runs exactly as in g1t's sandbox: the same harness, with a
+1−0
756756 Coding agents:
757757
758758 - [Connect a coding agent](https://docs.g1t.sh/guides/bring-your-own-agent/)
759+- [Build and ship an app with an agent](https://docs.g1t.sh/guides/build-and-ship/)
759760 - [Claude Code plugin](https://docs.g1t.sh/guides/claude-code-plugin/)
760761 - [Sessions, claims and dependencies](https://docs.g1t.sh/guides/sessions/)
761762 - [Sessions and why-blame](https://docs.g1t.sh/guides/why-blame/)

Comments

Sign in to comment.