Skip to content
Sign up

flagon-io/g1t

public
00

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
gitagentscloudflarerustforgemcp

Commit

Runner settings no longer say the merge queue runs jobs, and a dead link in repository settings is fixed (#52)

Since b5c43d31 the merge queue starts no jobs of its own (queue_build in services/work/src/queue.rs returns none), but the runner settings' descriptions and the workspace one's notes still said agents_on_self_hosted sends "the merge queue" to your runners. They now name what it sends: pull request checks and merge checks. update_repo_settings' notes linked what a repository can ask for in Working with g1t, a page that only redirects now and has no such anchor; they link Required checks in the Checks guide instead. The OpenAPI copy is regenerated.

Checked:
queue_build on main; the per-repository update_runner_settings entry has no notes to fix; cargo test -p g1t-api (209), -p g1t-contracts, -p g1t (ops table regenerated, unchanged by this); docs build, npm test, and id="required-checks" present in the built Checks guide.
G1t-Session:
ses_01m4ynr1peevvs8zwaqakycv2e
syntaqxcommitted Parenta835a02Browse files
3 files+6−60/3 viewed
+4−4
18431843 "A workspace's runner groups: which of its repositories may use the runners in each. The default group (every repository) is where runners go when no group is named. Owners only."
18441844 }
18451845 Op::GetRunnerSettings => {
1846− "Where a workspace's (or a repository's) own g1t jobs run, and whether pull requests from forks may use its self-hosted runners. `agents_on_self_hosted` sends checks and the merge queue to runners with `agent_labels` instead of g1t's sandboxes. A repository's are its workspace's unless it has its own (`inherited`)."
1846+ "Where a workspace's (or a repository's) own g1t jobs run, and whether pull requests from forks may use its self-hosted runners. `agents_on_self_hosted` sends pull request checks and merge checks to runners with `agent_labels` instead of g1t's sandboxes. A repository's are its workspace's unless it has its own (`inherited`)."
18471847 }
18481848 Op::CreateRunnerRegistrationToken => {
18491849 "A registration token for `g1t-runner register`, shown once. It lasts an hour and registers any number of runners until then, into `group` (the default group if none) for a workspace, or as a repository's own runners. It can do nothing else. Owners of the workspace, or admins of the repository, signed in or with a person's token; workspace tokens, G1T_TOKEN included, are refused."
18571857 Op::UpdateRunnerGroup => "Rename a runner group, or change which repositories may use it. Owners only.",
18581858 Op::DeleteRunnerGroup => "Delete a runner group. Its runners join the default group, which cannot be deleted. Owners only.",
18591859 Op::UpdateRunnerSettings => {
1860− "Change where g1t's own jobs (checks and the merge queue) run and whether pull requests from forks may use self-hosted runners, for a workspace or one repository. Left out is unchanged; `inherit` drops a repository's own settings. Allowing forks lets anyone who can open a pull request run code on your machines. Owners of the workspace, or admins of the repository."
1860+ "Change where g1t's own jobs (pull request checks and merge checks) run and whether pull requests from forks may use self-hosted runners, for a workspace or one repository. Left out is unchanged; `inherit` drops a repository's own settings. Allowing forks lets anyone who can open a pull request run code on your machines. Owners of the workspace, or admins of the repository."
18611861 }
18621862 Op::ImportIssue => {
18631863 "Open an issue from a ticket in Jira or Linear, or from a Sentry issue, by its key or address. The issue is linked to it: agents read the original, and when the work lands the ticket is told. Importing the same ticket again returns the issue already made."
31863186 ),
31873187 Op::UpdateRunnerSettings => object(
31883188 runners_owner(json!({
3189− "agents_on_self_hosted": { "type": "boolean", "description": "Run checks and the merge queue on self-hosted runners." },
3189+ "agents_on_self_hosted": { "type": "boolean", "description": "Run pull request checks and merge checks on self-hosted runners." },
31903190 "agent_labels": {
31913191 "type": "array",
31923192 "items": { "type": "string" },
3193− "description": "The labels a runner needs to take checks and merge queue work. self-hosted is always one.",
3193+ "description": "The labels a runner needs to take pull request checks and merge checks. self-hosted is always one.",
31943194 },
31953195 "fork_pull_requests": { "type": "boolean", "description": "Let jobs of pull requests from forks run on self-hosted runners." },
31963196 "inherit": { "type": "boolean", "description": "For a repository: drop its own settings and follow its workspace's." },
+2−2
10861086 "updated_by": "syntaqx",
10871087 "updated_at": "2026-10-04T16:20:37.508Z"
10881088 },
1089− "notes": "`required_checks` replaces the whole list: at most 20 names, each a workflow's name or another status's context, as [`list_check_names`](/reference/api/repositories/list-check-names/) gives them. A pull request merges only once each passes on its head; one nothing has reported holds it too. With the merge queue on, each must also pass on the queued state, so the workflows behind them need `merge_group` in their `on:`. `required_approvals` is at most 6. See [what a repository can ask for](/guides/working-with-g1t/#what-a-repository-can-ask-for). With `require_code_owner_review`, a pull request into the default branch merges only once the code owners of every file it changes have approved it, as many as each section of its CODEOWNERS file asks: see [Code owners](/guides/codeowners/). At least one of `allow_merge_commit`, `allow_squash_merge`, `allow_rebase_merge` and `allow_fast_forward` stays on, and `default_merge_method` must be one of them (`422` otherwise). `merge_commit_template` and `squash_commit_template` are used with `custom`: see [Commit messages](/guides/pull-requests/#commit-messages) for their placeholders. `has_issues` `null` goes back to the default: on for a repository, off for a fork. See [Repository settings](/guides/managing-repositories/#settings)."
1089+ "notes": "`required_checks` replaces the whole list: at most 20 names, each a workflow's name or another status's context, as [`list_check_names`](/reference/api/repositories/list-check-names/) gives them. A pull request merges only once each passes on its head; one nothing has reported holds it too. With the merge queue on, each must also pass on the queued state, so the workflows behind them need `merge_group` in their `on:`. `required_approvals` is at most 6. See [Required checks](/guides/checks/#required-checks). With `require_code_owner_review`, a pull request into the default branch merges only once the code owners of every file it changes have approved it, as many as each section of its CODEOWNERS file asks: see [Code owners](/guides/codeowners/). At least one of `allow_merge_commit`, `allow_squash_merge`, `allow_rebase_merge` and `allow_fast_forward` stays on, and `default_merge_method` must be one of them (`422` otherwise). `merge_commit_template` and `squash_commit_template` are used with `custom`: see [Commit messages](/guides/pull-requests/#commit-messages) for their placeholders. `has_issues` `null` goes back to the default: on for a repository, off for a fork. See [Repository settings](/guides/managing-repositories/#settings)."
10901090 },
10911091 "list_check_names": {
10921092 "response": [
47684768 "fork_pull_requests": false,
47694769 "inherited": false
47704770 },
4771− "notes": "`agents_on_self_hosted` and `agent_labels` keep their names from before g1t ran agents of its own: they now send g1t's own work (checks, merge checks and the merge queue) to your runners with those labels."
4771+ "notes": "`agents_on_self_hosted` and `agent_labels` keep their names from before g1t ran agents of its own: they now send g1t's own work (pull request checks and merge checks) to your runners with those labels."
47724772 },
47734773 "list_runner_groups": {
47744774 "params": {
+0−0

Binary or large file; its contents are not shown.

Comments

Sign in to comment.