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.

gitagentscloudflarerustforgemcp
syntaqxA pull request's merge options are read from what work keeps, not from the git store. GET /repos/flagon-io/g1t/pulls/41/merge-options took 8.0 to 8.6 s every time: merge_choices made the default merge messages from the branch's commits, and asked repos inspect_commits for them on every call, uncached. That call read the source's and the base's histories (1,000 commits each), worked out the merge base, fetched a pack from the git store and parsed it, asked identity who owns each signing key and address, and, for each of up to 250 commits, read its parent's tree and every changed level of both trees to list its files: all of it for messages that use only each commit's message and author. The site's stream gives up after 5 s, so the merge box never got its real choices and stayed on the settings-only box.

README.md

GitHub's workflow schema

workflow-v1.0.json is GitHub's schema for workflow files, copied unchanged from actions/languageservices, file workflow-parser/src/workflow-v1.0.json, at commit 4043eda158e16579cc5fb1b0b07a4bce2a76f0b5 (5 August 2026). It is MIT licensed; LICENSE is that repository's licence, copied from the same commit.

g1t does not read it at run time. src/syntax.rs lists the keys each part of a workflow may have, and its tests check those lists against this file, so they cannot drift from GitHub's. To update it, copy the file again, write the commit here, and run cargo test -p g1t-actions.