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
9 linesCodeBlameRaw

Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.

status.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas1-- Flagon, Inc. builds and runs g1t; its workspace runs comped, as
2-- g1t's own workspace does. The founder's personal workspace stays comped
3-- too (see 0008); either can be changed in sudo.g1t.sh.
4INSERT INTO billing_accounts (id, kind, name, terms_kind, note, terms_set_by, terms_set_at, created_by, created_at)
5VALUES ('ws_flagon-io', 'workspace', 'flagon-io', 'comped', 'Flagon, Inc., which builds g1t', 'migration', '2026-10-05T00:00:00Z', 'migration', '2026-10-05T00:00:00Z')
6ON CONFLICT (id) DO UPDATE SET terms_kind = 'comped', note = excluded.note, terms_set_by = 'migration', terms_set_at = excluded.terms_set_at;
7INSERT INTO admin_actions (id, account, action, detail, by, created_at)
8VALUES ('adm_migration_flagon_io', 'ws_flagon-io', 'terms', 'standard → comped: Flagon, Inc., which builds g1t', 'migration', '2026-10-05T00:00:00Z')
9ON CONFLICT (id) DO NOTHING;

This file's history is long; its oldest lines are credited to the oldest commit read.