apps/web/app/routes/repo · flagon-io/g1t

about-json.tsMerge branch 'main' into worktree-agent-a69aeabc4b0deeb971w ago

actions-artifact.tsThe artifacts service is services/artifacts, the Worker g1t-artifacts, bound as ARTIFACTS by the API, the site and the agents; its live rooms move to it with a Durable Object transfer from g1t-docs-service, and its database, bucket, indexes and queue keep their names. The git store's binding and settings are GITSTORE, its ops scripts gitstore-*, and workflow run artifacts keep their compatible API under run_artifacts modules. The deploy tool puts a Worker that has never deployed before the Workers in its stage that bind to it, and the deploy guide gives the cutover runbook.6d ago

actions-badge.tsMerge Actions runs: summaries, attempts and re-runs, graceful cancel, log downloads, badges (actions 0009)1w ago

actions-job-log-download.tsMerge Actions runs: summaries, attempts and re-runs, graceful cancel, log downloads, badges (actions 0009)1w ago

actions-log.ts

actions-logs-download.tsMerge Actions runs: summaries, attempts and re-runs, graceful cancel, log downloads, badges (actions 0009)1w ago

actions-run.tsxPeople wear their own avatars wherever g1t knows them only by name, and a workspace is never shown as a person. The activity feeds, recent changes, home's most active faces, issue and pull request authors, assignees, comments and the audit log drew a person from their username alone, so everyone got their letter avatar instead of the picture they uploaded. An avatar given no picture now draws the letter at once and lays the person's own picture over it once it loads, from /-/avatar/user/<username> (routes/avatar-user.ts): a redirect to the picture on the usercontent origin, or not found, read from identity's people only, so a workspace's icon can never stand in for someone. Kept five minutes, public like the profile. Agents, the product tour's people, "someone" and workspaces' square avatars are never looked up (image null), so an account with the same name never lends them its face.3d ago

actions.tsxMerge main into rm-agents: mirroring removal, open signups, free-tier limits, the g1t CLI and runner fixes, with the agent removal kept. The CLI's table of operations is regenerated from the API without the agent, customize and AI credit operations; no CLI command used them.4d ago

activity.tsxPeople wear their own avatars wherever g1t knows them only by name, and a workspace is never shown as a person. The activity feeds, recent changes, home's most active faces, issue and pull request authors, assignees, comments and the audit log drew a person from their username alone, so everyone got their letter avatar instead of the picture they uploaded. An avatar given no picture now draws the letter at once and lays the person's own picture over it once it loads, from /-/avatar/user/<username> (routes/avatar-user.ts): a redirect to the picture on the usercontent origin, or not found, read from identity's people only, so a workspace's icon can never stand in for someone. Kept five minutes, public like the profile. Agents, the product tour's people, "someone" and workspaces' square avatars are never looked up (image null), so an account with the same name never lends them its face.3d ago

add-ci.tsMerge main into rm-agents: mirroring removal, open signups, free-tier limits, the g1t CLI and runner fixes, with the agent removal kept. The CLI's table of operations is regenerated from the API without the agent, customize and AI credit operations; no CLI command used them.4d ago

archive.tsMerge GitHub pull request #8 (claude/cool-newton-7nm8r9): Docker deployments on g1t.page behind a switch that stays off until Cloudflare's container APIs are checked live, workflows a workspace manages in its repositories, tarball and zipball downloads, refs/pull/* kept to g1t alone, framework detection for g1t.page builds, and a workflow's event payload matching GitHub's.4d ago

blame-data.tsMerge remote-tracking branch 'g1t/main' into HEADyesterday

blob.tsxMerge remote-tracking branch 'g1t/main' into HEADyesterday

branch-names.tsTeams and CODEOWNERS, labels and milestones, dependency updates, the security suite, and a clearer top bar1w ago

branches.tsxA page's tabs are paths, not ?tab= (#52 ): a profile's are /u/syntaqx/pulls, /issues and /stars; a pull request's Session and Files changed are /pull/12/session and /pull/12/files (the segment the desktop and phone links and the analytics already expected); the Branches page's are /branches/yours, /active, /stale and /all; rules' Insights is /settings/rules/insights and /<workspace>/-/rules/insights; and Notifications' Saved and Done are /notifications/saved and /notifications/done. A tab that is a page of its own gets an address of its own, which reads, shares and bookmarks well. What narrows a list stays in the query: state, repo, sort and before on a profile; q on Branches; branch, tag, problems and before on Rules; and on Notifications the severity tabs (?tab=needs and the like, which narrow any view and are kept as the panel in the top bar fetches them) and reason. The package page's ?tab=settings stays too: its name is a splat that can itself end in /settings (an npm package @acme/settings).yesterday

check-run.tsxThe site is built from its shared components: one Button with its variants and sizes, one Badge, Card for every panel, Alert for notices, Kbd for keys, Table for the security tables, and Avatar, Command, Progress, ScrollArea, ToggleGroup, Collapsible and Accordion in the kit; raw buttons, hand-drawn cards and pills and per-file button class lists are gone, outline buttons stand the same height as filled ones, and the phone's Ask g1t loses its tile. Every page was compared pixel by pixel before and after.6d ago

code.tsxMerge branch 'forking': repository forking, pull request merge methods and every repository setting for pull requests, commits, pushes and issues2d ago

commit.tsxA page's tabs are paths, not ?tab= (#52 ): a profile's are /u/syntaqx/pulls, /issues and /stars; a pull request's Session and Files changed are /pull/12/session and /pull/12/files (the segment the desktop and phone links and the analytics already expected); the Branches page's are /branches/yours, /active, /stale and /all; rules' Insights is /settings/rules/insights and /<workspace>/-/rules/insights; and Notifications' Saved and Done are /notifications/saved and /notifications/done. A tab that is a page of its own gets an address of its own, which reads, shares and bookmarks well. What narrows a list stays in the query: state, repo, sort and before on a profile; q on Branches; branch, tag, problems and before on Rules; and on Notifications the severity tabs (?tab=needs and the like, which narrow any view and are kept as the panel in the top bar fetches them) and reason. The package page's ?tab=settings stays too: its name is a splat that can itself end in /settings (an npm package @acme/settings).yesterday

commits.tsxMerge main into project-descriptionsyesterday

compare.tsxMerge main into project-descriptionsyesterday

contributors.tsxPeople wear their own avatars wherever g1t knows them only by name, and a workspace is never shown as a person. The activity feeds, recent changes, home's most active faces, issue and pull request authors, assignees, comments and the audit log drew a person from their username alone, so everyone got their letter avatar instead of the picture they uploaded. An avatar given no picture now draws the letter at once and lays the person's own picture over it once it loads, from /-/avatar/user/<username> (routes/avatar-user.ts): a redirect to the picture on the usercontent origin, or not found, read from identity's people only, so a workspace's icon can never stand in for someone. Kept five minutes, public like the profile. Agents, the product tour's people, "someone" and workspaces' square avatars are never looked up (image null), so an account with the same name never lends them its face.3d ago

deployment.tsxA project's pages line up with its header and tabs. Deployments, a deployment, an observability request, Observability settings, New release and the Soon pages each centred themselves in a narrower box inside the project's own, so their content sat indented on both sides while Observability, Issues and the rest ran the full width; Usage added the page's padding a second time. They now start at the same edge: lists and detail pages take the full width, and the forms and Soon pages keep their reading width from the left. Checked: the site's typecheck (tsc -b --force), its 911 tests and a production build.2d ago

deployments.tsxAn app that deploys itself says so, instead of "Deployed elsewhere". A project whose own workflows (or another pipeline) deploy it, as g1t's do, read as if g1t had nothing to do with it: grey "Deployed elsewhere" in the workspace's Projects, "App, deployed elsewhere" on its badge, and the API said `runs` is `g1t` "when g1t deploys it". What tells the two apart is who hosts it, so they are now named that way: App or site, hosted on g1t.page (badge App on g1t.page) and App or site that deploys itself (badge App, deploys itself), in settings, the badge's menu, the overview's "Where does it run?" (It deploys itself), the Deployments pages, the guides and the API's descriptions; `runs` keeps its values. In Projects an app that deploys itself shows the rocket, Deploys itself, and the Deploys filter counts it. Its production card says which workflow run deployed it when g1t Actions did ("deployed 16m ago by its workflow"), else "by its own pipeline". An app nobody has placed that deploys production itself (a successful production deployment from a workflow or the API, not g1t.page's) now deploys itself everywhere, where before only its overview inferred it: the projects service keeps that it has (migration 0013, `reports_production`), and Deployments being on or a setting still win. Checked: the site's typecheck (tsc -b --force), its 911 tests and a production build; the projects service's typecheck and 49 tests (new: an app that deploys production itself); the API's openapi tests with the docs copy regenerated; the deploy tool's 92 tests.2d ago

diff-files.tsMerge branch 'worktree-agent-a432c4ed9deb834b1'3d ago

fork.tsxSearch shows every repository's own project's description, also where the project had one of its own before #45 . Search kept repositories' descriptions until then, so such a project still showed the repository's old text there and on Explore. Projects now tells search every one once: the first listing or lookup after this deploys publishes project.updated for each repository's own project with a description, after its answer is sent, claimed by a row in the new sweeps table so it runs once for all of g1t. The fork form also says what a fork's project starts with, not that a description is copied. Checked: projects' type-check and tests (47), its migrations on local D1, and node --test scripts/deploy (92). Looked at signed-in: the repository header and About, Repository and General settings, the New project and fork forms, the workspace's Repositories, a repository's forks, and the AI page's Anthropic form.yesterday

forks.tsxOnly projects have descriptions now; a repository no longer keeps one of its own (#45 ). Every repository already had a project of its own name, which showed the repository's description until it was given another, so the same line lived in two places with two settings pages. Now:yesterday

invitations.tsxMerge remote-tracking branch 'origin/claude/cool-newton-7nm8r9' into claude/cool-newton-7nm8r94d ago

issue-new.tsxThe contracts no longer describe g1t's own agents, and workspaces can keep their AI providers. Every consumer had already stopped using them, so the TypeScript and Rust contracts drop the workspace-agent, ability, look, skill-library, context, runner-agent and mention modules, the chat and docs RPCs agents posted and read through, the folio agent methods, the agent_waiting notification, agent.asked and memory.changed events, AI credit, token and gateway billing types, model routes and sessions, team agents, agent tokens, plan, review, message and confidence types, command rules, cost caps and confidence rules. The agents:run and models:* scopes are no longer offered by any preset, OAuth default or permission form, but a stored token or grant that names them still reads; and the removed operations are gone from the scope table, so the API's check that every operation has exactly one scope is strict again. What stored data needs in order to parse (old run and credential kinds, an agent team lead, retired rules and webhook events, old guardrail and integration settings) still parses, and a run's token is still PrincipalKind::Agent, which now means a run's token and the @g1t rows written before. The customize, marketplace, skills and claude-plugin contracts stay only until the mobile app drops its Customize screens.4d ago

issue.tsxMerge main into project-descriptionsyesterday

issues.tsxMerge main into project-descriptionsyesterday

labels.tsxMerge main into rm-agents: mirroring removal, open signups, free-tier limits, the g1t CLI and runner fixes, with the agent removal kept. The CLI's table of operations is regenerated from the API without the agent, customize and AI credit operations; no CLI command used them.4d ago

layout.tsxOnly projects have descriptions now; a repository no longer keeps one of its own (#45 ). Every repository already had a project of its own name, which showed the repository's description until it was given another, so the same line lived in two places with two settings pages. Now:yesterday

milestone.tsxThe site is built from its shared components: one Button with its variants and sizes, one Badge, Card for every panel, Alert for notices, Kbd for keys, Table for the security tables, and Avatar, Command, Progress, ScrollArea, ToggleGroup, Collapsible and Accordion in the kit; raw buttons, hand-drawn cards and pills and per-file button class lists are gone, outline buttons stand the same height as filled ones, and the phone's Ask g1t loses its tile. Every page was compared pixel by pixel before and after.6d ago

milestones.tsxThe site is built from its shared components: one Button with its variants and sizes, one Badge, Card for every panel, Alert for notices, Kbd for keys, Table for the security tables, and Avatar, Command, Progress, ScrollArea, ToggleGroup, Collapsible and Accordion in the kit; raw buttons, hand-drawn cards and pills and per-file button class lists are gone, outline buttons stand the same height as filled ones, and the phone's Ask g1t loses its tile. Every page was compared pixel by pixel before and after.6d ago

notifications.tsInbox on the site: reasons, a reason filter, Subscribe, Watch and settings1w ago

observability-errors.tsxPeople wear their own avatars wherever g1t knows them only by name, and a workspace is never shown as a person. The activity feeds, recent changes, home's most active faces, issue and pull request authors, assignees, comments and the audit log drew a person from their username alone, so everyone got their letter avatar instead of the picture they uploaded. An avatar given no picture now draws the letter at once and lays the person's own picture over it once it loads, from /-/avatar/user/<username> (routes/avatar-user.ts): a redirect to the picture on the usercontent origin, or not found, read from identity's people only, so a workspace's icon can never stand in for someone. Kept five minutes, public like the profile. Agents, the product tour's people, "someone" and workspaces' square avatars are never looked up (image null), so an account with the same name never lends them its face.3d ago

observability-live.tsProjects have Observability: their requests, logs, traces, metrics and errors, from apps on g1t.page with nothing to set up, and from software anywhere else over OpenTelemetry.4d ago

observability-logs.tsxProjects have Observability: their requests, logs, traces, metrics and errors, from apps on g1t.page with nothing to set up, and from software anywhere else over OpenTelemetry.4d ago

observability-metrics.tsxPeople wear their own avatars wherever g1t knows them only by name, and a workspace is never shown as a person. The activity feeds, recent changes, home's most active faces, issue and pull request authors, assignees, comments and the audit log drew a person from their username alone, so everyone got their letter avatar instead of the picture they uploaded. An avatar given no picture now draws the letter at once and lays the person's own picture over it once it loads, from /-/avatar/user/<username> (routes/avatar-user.ts): a redirect to the picture on the usercontent origin, or not found, read from identity's people only, so a workspace's icon can never stand in for someone. Kept five minutes, public like the profile. Agents, the product tour's people, "someone" and workspaces' square avatars are never looked up (image null), so an account with the same name never lends them its face.3d ago

observability-request.tsxA project's pages line up with its header and tabs. Deployments, a deployment, an observability request, Observability settings, New release and the Soon pages each centred themselves in a narrower box inside the project's own, so their content sat indented on both sides while Observability, Issues and the rest ran the full width; Usage added the page's padding a second time. They now start at the same edge: lists and detail pages take the full width, and the forms and Soon pages keep their reading width from the left. Checked: the site's typecheck (tsc -b --force), its 911 tests and a production build.2d ago

observability-requests.tsxProjects have Observability: their requests, logs, traces, metrics and errors, from apps on g1t.page with nothing to set up, and from software anywhere else over OpenTelemetry.4d ago

observability-settings.tsxA project's pages line up with its header and tabs. Deployments, a deployment, an observability request, Observability settings, New release and the Soon pages each centred themselves in a narrower box inside the project's own, so their content sat indented on both sides while Observability, Issues and the rest ran the full width; Usage added the page's padding a second time. They now start at the same edge: lists and detail pages take the full width, and the forms and Soon pages keep their reading width from the left. Checked: the site's typecheck (tsc -b --force), its 911 tests and a production build.2d ago

observability-trace.tsxProjects have Observability: their requests, logs, traces, metrics and errors, from apps on g1t.page with nothing to set up, and from software anywhere else over OpenTelemetry.4d ago

observability-traces.tsxProjects have Observability: their requests, logs, traces, metrics and errors, from apps on g1t.page with nothing to set up, and from software anywhere else over OpenTelemetry.4d ago

observability.tsxPeople wear their own avatars wherever g1t knows them only by name, and a workspace is never shown as a person. The activity feeds, recent changes, home's most active faces, issue and pull request authors, assignees, comments and the audit log drew a person from their username alone, so everyone got their letter avatar instead of the picture they uploaded. An avatar given no picture now draws the letter at once and lays the person's own picture over it once it loads, from /-/avatar/user/<username> (routes/avatar-user.ts): a redirect to the picture on the usercontent origin, or not found, read from identity's people only, so a workspace's icon can never stand in for someone. Kept five minutes, public like the profile. Agents, the product tour's people, "someone" and workspaces' square avatars are never looked up (image null), so an account with the same name never lends them its face.3d ago

overview.tsxMerge branch 'worktree-agent-a9934473c8cf2bca6'3d ago

production-elsewhere.tsMerge branch 'worktree-agent-a5b0d9e2733e9e382'4d ago

production-screenshot.tsMerge g1tusercontent.com: registry answers run nothing in a browser, the site's pages run only their own scripts, repository files and avatars on their own origin, raw files rate limited per address1w ago

pull-new.tsxMerge branch 'forking': repository forking, pull request merge methods and every repository setting for pull requests, commits, pushes and issues2d ago

pull.tsxA page's tabs are paths, not ?tab= (#52 ): a profile's are /u/syntaqx/pulls, /issues and /stars; a pull request's Session and Files changed are /pull/12/session and /pull/12/files (the segment the desktop and phone links and the analytics already expected); the Branches page's are /branches/yours, /active, /stale and /all; rules' Insights is /settings/rules/insights and /<workspace>/-/rules/insights; and Notifications' Saved and Done are /notifications/saved and /notifications/done. A tab that is a page of its own gets an address of its own, which reads, shares and bookmarks well. What narrows a list stays in the query: state, repo, sort and before on a profile; q on Branches; branch, tag, problems and before on Rules; and on Notifications the severity tabs (?tab=needs and the like, which narrow any view and are kept as the panel in the top bar fetches them) and reason. The package page's ?tab=settings stays too: its name is a splat that can itself end in /settings (an npm package @acme/settings).yesterday

pulls.tsxThe site no longer has g1t's own agents. g1t is where the coding agents you already use do their work, so the Agents mode is gone from the rail, with every page under /<workspace>/-/agents: personas, faces, skills, abilities, routines, computers, sessions and agent spend. Customize (skills, connectors, plugins, marketplaces), the context hub, model providers, the AI Gateway page, the Spend page and pill, Ask g1t, and the repository's Agents, Plans and agent settings pages go too, and their addresses now answer 404.4d ago

queue.tsxMerge branch 'worktree-agent-aa68cf6ecc03dffaf'3d ago

raw.tsMerge g1tusercontent.com: registry answers run nothing in a browser, the site's pages run only their own scripts, repository files and avatars on their own origin, raw files rate limited per address1w ago

ref-card.tsMerge main into project-descriptionsyesterday

release-new.tsxA project's pages line up with its header and tabs. Deployments, a deployment, an observability request, Observability settings, New release and the Soon pages each centred themselves in a narrower box inside the project's own, so their content sat indented on both sides while Observability, Issues and the rest ran the full width; Usage added the page's padding a second time. They now start at the same edge: lists and detail pages take the full width, and the forms and Soon pages keep their reading width from the left. Checked: the site's typecheck (tsc -b --force), its 911 tests and a production build.2d ago

release.tsxThe site is built from its shared components: one Button with its variants and sizes, one Badge, Card for every panel, Alert for notices, Kbd for keys, Table for the security tables, and Avatar, Command, Progress, ScrollArea, ToggleGroup, Collapsible and Accordion in the kit; raw buttons, hand-drawn cards and pills and per-file button class lists are gone, outline buttons stand the same height as filled ones, and the phone's Ask g1t loses its tile. Every page was compared pixel by pixel before and after.6d ago

releases.tsxMerge branch 'main' into worktree-agent-a69aeabc4b0deeb971w ago

secrets.tsxInvite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look1w ago

security-advisories.tsxMerge remote-tracking branch 'origin/claude/cool-newton-7nm8r9' into claude/cool-newton-7nm8r94d ago

security-advisory-edit.tsxMerge remote-tracking branch 'origin/claude/cool-newton-7nm8r9' into claude/cool-newton-7nm8r94d ago

security-advisory.tsxMerge remote-tracking branch 'origin/claude/cool-newton-7nm8r9' into claude/cool-newton-7nm8r94d ago

security-code-alert.tsxPeople wear their own avatars wherever g1t knows them only by name, and a workspace is never shown as a person. The activity feeds, recent changes, home's most active faces, issue and pull request authors, assignees, comments and the audit log drew a person from their username alone, so everyone got their letter avatar instead of the picture they uploaded. An avatar given no picture now draws the letter at once and lays the person's own picture over it once it loads, from /-/avatar/user/<username> (routes/avatar-user.ts): a redirect to the picture on the usercontent origin, or not found, read from identity's people only, so a workspace's icon can never stand in for someone. Kept five minutes, public like the profile. Agents, the product tour's people, "someone" and workspaces' square avatars are never looked up (image null), so an account with the same name never lends them its face.3d ago

security-code-setup.tsMerge main into rm-agents: mirroring removal, open signups, free-tier limits, the g1t CLI and runner fixes, with the agent removal kept. The CLI's table of operations is regenerated from the API without the agent, customize and AI credit operations; no CLI command used them.4d ago

security-code.tsxPeople wear their own avatars wherever g1t knows them only by name, and a workspace is never shown as a person. The activity feeds, recent changes, home's most active faces, issue and pull request authors, assignees, comments and the audit log drew a person from their username alone, so everyone got their letter avatar instead of the picture they uploaded. An avatar given no picture now draws the letter at once and lays the person's own picture over it once it loads, from /-/avatar/user/<username> (routes/avatar-user.ts): a redirect to the picture on the usercontent origin, or not found, read from identity's people only, so a workspace's icon can never stand in for someone. Kept five minutes, public like the profile. Agents, the product tour's people, "someone" and workspaces' square avatars are never looked up (image null), so an account with the same name never lends them its face.3d ago

security-graph.tsxPeople wear their own avatars wherever g1t knows them only by name, and a workspace is never shown as a person. The activity feeds, recent changes, home's most active faces, issue and pull request authors, assignees, comments and the audit log drew a person from their username alone, so everyone got their letter avatar instead of the picture they uploaded. An avatar given no picture now draws the letter at once and lays the person's own picture over it once it loads, from /-/avatar/user/<username> (routes/avatar-user.ts): a redirect to the picture on the usercontent origin, or not found, read from identity's people only, so a workspace's icon can never stand in for someone. Kept five minutes, public like the profile. Agents, the product tour's people, "someone" and workspaces' square avatars are never looked up (image null), so an account with the same name never lends them its face.3d ago

security-overview.tsxMerge branch 'worktree-agent-a5c94df323642630e'4d ago

security-patterns.tsxPricing says it plainly: models at the provider's price, the agent rate for what g1t runs around every model call (the gateway, secrets, routing, context and pass-through to your own provider, so your own keys too), everything else at cost plus 20%, your own runners free, no seats; Security and quality comes with the plan with no separate fee, and live activations end. Each agent has an effort setting, Auto to Max, with what a typical task has cost at each level, and Spend's Spend less, keep quality suggests a lower level only when the agent's own past work shows quality held, to apply or dismiss. The pricing, spend and agents guides say how.6d ago

security-policy-setup.tsMerge main into rm-agents: mirroring removal, open signups, free-tier limits, the g1t CLI and runner fixes, with the agent removal kept. The CLI's table of operations is regenerated from the API without the agent, customize and AI credit operations; no CLI command used them.4d ago

security-pull.tsxMerge commit '9232a85b'2d ago

security-report.tsxMerge remote-tracking branch 'origin/claude/cool-newton-7nm8r9' into claude/cool-newton-7nm8r94d ago

security-reports.tsxMerge remote-tracking branch 'origin/claude/cool-newton-7nm8r9' into claude/cool-newton-7nm8r94d ago

security-sbom.tsTeams and CODEOWNERS, labels and milestones, dependency updates, the security suite, and a clearer top bar1w ago

security-secret.tsxThe site no longer has g1t's own agents. g1t is where the coding agents you already use do their work, so the Agents mode is gone from the rail, with every page under /<workspace>/-/agents: personas, faces, skills, abilities, routines, computers, sessions and agent spend. Customize (skills, connectors, plugins, marketplaces), the context hub, model providers, the AI Gateway page, the Spend page and pill, Ask g1t, and the repository's Agents, Plans and agent settings pages go too, and their addresses now answer 404.4d ago

security-secrets.tsxMerge branch 'worktree-agent-a5c94df323642630e'4d ago

security-settings.tsxMerge remote-tracking branch 'origin/claude/cool-newton-7nm8r9' into claude/cool-newton-7nm8r94d ago

security-updates.tsxTeams and CODEOWNERS, labels and milestones, dependency updates, the security suite, and a clearer top bar1w ago

security.tsxMerge main into rm-agents: mirroring removal, open signups, free-tier limits, the g1t CLI and runner fixes, with the agent removal kept. The CLI's table of operations is regenerated from the API without the agent, customize and AI credit operations; no CLI command used them.4d ago

session.tsxMerge branch 'worktree-agent-aa68cf6ecc03dffaf'3d ago

sessions.tsxPeople wear their own avatars wherever g1t knows them only by name, and a workspace is never shown as a person. The activity feeds, recent changes, home's most active faces, issue and pull request authors, assignees, comments and the audit log drew a person from their username alone, so everyone got their letter avatar instead of the picture they uploaded. An avatar given no picture now draws the letter at once and lays the person's own picture over it once it loads, from /-/avatar/user/<username> (routes/avatar-user.ts): a redirect to the picture on the usercontent origin, or not found, read from identity's people only, so a workspace's icon can never stand in for someone. Kept five minutes, public like the profile. Agents, the product tour's people, "someone" and workspaces' square avatars are never looked up (image null), so an account with the same name never lends them its face.3d ago

settings-access.tsxPeople wear their own avatars wherever g1t knows them only by name, and a workspace is never shown as a person. The activity feeds, recent changes, home's most active faces, issue and pull request authors, assignees, comments and the audit log drew a person from their username alone, so everyone got their letter avatar instead of the picture they uploaded. An avatar given no picture now draws the letter at once and lays the person's own picture over it once it loads, from /-/avatar/user/<username> (routes/avatar-user.ts): a redirect to the picture on the usercontent origin, or not found, read from identity's people only, so a workspace's icon can never stand in for someone. Kept five minutes, public like the profile. Agents, the product tour's people, "someone" and workspaces' square avatars are never looked up (image null), so an account with the same name never lends them its face.3d ago

settings-actions.tsxMerge branch 'forking': repository forking, pull request merge methods and every repository setting for pull requests, commits, pushes and issues2d ago

settings-branches.tsxMerge branch 'forking': repository forking, pull request merge methods and every repository setting for pull requests, commits, pushes and issues2d ago

settings-deploy-keys.tsxPeople wear their own avatars wherever g1t knows them only by name, and a workspace is never shown as a person. The activity feeds, recent changes, home's most active faces, issue and pull request authors, assignees, comments and the audit log drew a person from their username alone, so everyone got their letter avatar instead of the picture they uploaded. An avatar given no picture now draws the letter at once and lays the person's own picture over it once it loads, from /-/avatar/user/<username> (routes/avatar-user.ts): a redirect to the picture on the usercontent origin, or not found, read from identity's people only, so a workspace's icon can never stand in for someone. Kept five minutes, public like the profile. Agents, the product tour's people, "someone" and workspaces' square avatars are never looked up (image null), so an account with the same name never lends them its face.3d ago

settings-deployments.tsxAn app that deploys itself says so, instead of "Deployed elsewhere". A project whose own workflows (or another pipeline) deploy it, as g1t's do, read as if g1t had nothing to do with it: grey "Deployed elsewhere" in the workspace's Projects, "App, deployed elsewhere" on its badge, and the API said `runs` is `g1t` "when g1t deploys it". What tells the two apart is who hosts it, so they are now named that way: App or site, hosted on g1t.page (badge App on g1t.page) and App or site that deploys itself (badge App, deploys itself), in settings, the badge's menu, the overview's "Where does it run?" (It deploys itself), the Deployments pages, the guides and the API's descriptions; `runs` keeps its values. In Projects an app that deploys itself shows the rocket, Deploys itself, and the Deploys filter counts it. Its production card says which workflow run deployed it when g1t Actions did ("deployed 16m ago by its workflow"), else "by its own pipeline". An app nobody has placed that deploys production itself (a successful production deployment from a workflow or the API, not g1t.page's) now deploys itself everywhere, where before only its overview inferred it: the projects service keeps that it has (migration 0013, `reports_production`), and Deployments being on or a setting still win. Checked: the site's typecheck (tsc -b --force), its 911 tests and a production build; the projects service's typecheck and 49 tests (new: an app that deploys production itself); the API's openapi tests with the docs copy regenerated; the deploy tool's 92 tests.2d ago

settings-domains.tsxMoney is written one way. A single formatter turns millionths of a dollar into dollars, rounding half up on whole micros rather than on a float, so the same sum reads the same on every page: under a cent reads <$0.01 on a total and exactly nothing is $0.00, while the statement's lines, a session's receipt, the price book and an agent's effort costs carry up to four places where the fraction of a cent is the point; the six formatters that each rounded their own way are gone. This month is the calendar month in UTC from its first day to today everywhere, and billing counts the month's not-yet-closed usage in any range that reaches into the current month, so the top bar's pill, Spend, Home and Usage ask for the same days and get the same figure; Home now reads the usage report the others read instead of adding up statements. Usage's pending sentence says what of that usage the close will charge after the discount and included usage, which the billing API returns as pending_charged_micros. A reconciliation test holds the pill, Spend, Home and Usage to one number for one month. The usage and billing guide says how amounts are written and what this month means.6d ago

settings-environments.tsxMerge remote-tracking branch 'origin/claude/cool-newton-7nm8r9' into claude/cool-newton-7nm8r94d ago

settings-guardrails.tsxMerge branch 'main' into ask-integration3d ago

settings-repository.tsxOnly projects have descriptions now; a repository no longer keeps one of its own (#45 ). Every repository already had a project of its own name, which showed the repository's description until it was given another, so the same line lived in two places with two settings pages. Now:yesterday

settings-rules.tsxA page's tabs are paths, not ?tab= (#52 ): a profile's are /u/syntaqx/pulls, /issues and /stars; a pull request's Session and Files changed are /pull/12/session and /pull/12/files (the segment the desktop and phone links and the analytics already expected); the Branches page's are /branches/yours, /active, /stale and /all; rules' Insights is /settings/rules/insights and /<workspace>/-/rules/insights; and Notifications' Saved and Done are /notifications/saved and /notifications/done. A tab that is a page of its own gets an address of its own, which reads, shares and bookmarks well. What narrows a list stays in the query: state, repo, sort and before on a profile; q on Branches; branch, tag, problems and before on Rules; and on Notifications the severity tabs (?tab=needs and the like, which narrow any view and are kept as the panel in the top bar fetches them) and reason. The package page's ?tab=settings stays too: its name is a splat that can itself end in /settings (an npm package @acme/settings).yesterday

settings-ruleset.tsxMerge rulesets: branch and tag rules, agent-first, enforced on push and merge1w ago

settings-runners.tsxFast pages, required checks on the branch, self-hosted runners, honest incidents1w ago

settings.tsxOnly projects have descriptions now; a repository no longer keeps one of its own (#45 ). Every repository already had a project of its own name, which showed the repository's description until it was given another, so the same line lived in two places with two settings pages. Now:yesterday

soon.tsxA project's pages line up with its header and tabs. Deployments, a deployment, an observability request, Observability settings, New release and the Soon pages each centred themselves in a narrower box inside the project's own, so their content sat indented on both sides while Observability, Issues and the rest ran the full width; Usage added the page's padding a second time. They now start at the same edge: lists and detail pages take the full width, and the forms and Soon pages keep their reading width from the left. Checked: the site's typecheck (tsc -b --force), its 911 tests and a production build.2d ago

star.tsMerge branch 'main' into worktree-agent-a69aeabc4b0deeb971w ago

stargazers.tsxThe site is built from its shared components: one Button with its variants and sizes, one Badge, Card for every panel, Alert for notices, Kbd for keys, Table for the security tables, and Avatar, Command, Progress, ScrollArea, ToggleGroup, Collapsible and Accordion in the kit; raw buttons, hand-drawn cards and pills and per-file button class lists are gone, outline buttons stand the same height as filled ones, and the phone's Ask g1t loses its tile. Every page was compared pixel by pixel before and after.6d ago

sync-fork.tsMerge branch 'forking': repository forking, pull request merge methods and every repository setting for pull requests, commits, pushes and issues2d ago

tags.tsxMerge main into project-descriptionsyesterday

tree.tsxMerge branch 'forking': repository forking, pull request merge methods and every repository setting for pull requests, commits, pushes and issues2d ago

usage.tsxA project's pages line up with its header and tabs. Deployments, a deployment, an observability request, Observability settings, New release and the Soon pages each centred themselves in a narrower box inside the project's own, so their content sat indented on both sides while Observability, Issues and the rest ran the full width; Usage added the page's padding a second time. They now start at the same edge: lists and detail pages take the full width, and the forms and Soon pages keep their reading width from the left. Checked: the site's typecheck (tsc -b --force), its 911 tests and a production build.2d ago

webhooks.tsxInvite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look1w ago

why.tsMerge branch 'worktree-agent-aa68cf6ecc03dffaf'3d ago

work-session.tsxAgents in any harness coordinate through one inbox, the merge queue lands only what an attempt itself tested, and workspaces have Insights. Each session keeps the coordination updates that concern it (session_updates, migration 0038): claims, releases, hand-offs and expiries, overlaps, dependency changes, decisions, integration results and sessions starting and ending, about the issues and pull requests it is on or tied to, or every one while it is on nothing yet; never its own start, end or claims. An update is written in the same batch as the change it announces, guarded so it exists only once the change is made, with an id derived from the change, so a retry or two requests at once deliver it once; a blocker clearing and queue results follow their change under a key that names it. get_session's `updates` lists up to 100, oldest first, and reading never clears them; record_session_entries' `acknowledge` clears exact IDs for that session only and says how many were its (`acknowledged`). The CLI has `g1t session updates` and `g1t session acknowledge ID --note` (the decision note and the acknowledgement in one idempotent call, `--session` over G1T_SESSION), and those and `heartbeat` say which files the working copy changed (git status; G1T_TOUCH=0 turns it off), so overlapping edits are noticed whichever harness makes them; a pair of sessions is told again when another file in common joins. The Claude Code hooks fetch the inbox in the background, show it at every prompt and before tools when it changes or every two minutes, refresh after an acknowledgement, and never acknowledge. The AGENTS.md snippet, the skills, MCP's instructions and llms.txt say the same steps for every harness: scope claims (Scope, Interfaces, Depends on, Checks), proceed on complementary work, agree ownership before overlapping edits, record public summaries and evidence, never private reasoning. Claims resolve ownership in one statement, so simultaneous claims by one session converge. The merge queue: every attempt has its own id and branch (0037); a claimed build, an accepted build, a report and a callback each check their attempt; a dispatch registers its runs first and Actions fails the dispatch when it cannot; an attempt is decided only by its own runs (and other tools' statuses set after it was claimed), never an earlier attempt's or the pull request's own on the same commit (0040 keeps what it built and how many runs it registered); landing re-reads the rules, honours a bypass asked for when queued (0039), checks no predecessor remains, carries the exact tested commit to Git's compare-and-swap, records publication intent that fences removal, closing, drafting and changing base, resumes after a crash, and a publisher that lost a race no longer undoes the winner's landing; a retried attempt's branch is deleted; an entry whose branch or pull request is gone leaves the queue with a note instead of blocking those behind it; diagnosis rebuilds exactly what was tested and names a failing combination, not a proven cause. A session's page shows what awaits its agent as the coordination feed does. Workspace Insights (/:owner/-/insights): delivery metrics across a workspace's readable repositories (work service delivery_insights). Deploy Work migrations 0037 to 0040 first (the pipeline does), then Repos and Actions before Work, and the site with Work. Checked: cargo test for g1t-work (143), g1t-repos (311), g1t-actions-service (108), g1t-api (201), g1t (149), g1t-rules (72), g1t-contracts (306) and wasm32 builds; cargo check --workspace; the conformance suite against freshly built API and Work Workers (5, none skipped); the Claude Code hooks (49); the site's typecheck, tests (919) and a production build; the deploy tool's 92 tests; the docs build; and two unscripted local rehearsals in which two concurrent agents, given only a task and AGENTS.md, found each other, agreed a split and made complementary edits.2d ago

work.tsxA page's tabs are paths, not ?tab= (#52 ): a profile's are /u/syntaqx/pulls, /issues and /stars; a pull request's Session and Files changed are /pull/12/session and /pull/12/files (the segment the desktop and phone links and the analytics already expected); the Branches page's are /branches/yours, /active, /stale and /all; rules' Insights is /settings/rules/insights and /<workspace>/-/rules/insights; and Notifications' Saved and Done are /notifications/saved and /notifications/done. A tab that is a page of its own gets an address of its own, which reads, shares and bookmarks well. What narrows a list stays in the query: state, repo, sort and before on a profile; q on Branches; branch, tag, problems and before on Rules; and on Notifications the severity tabs (?tab=needs and the like, which narrow any view and are kept as the panel in the top bar fetches them) and reason. The package page's ?tab=settings stays too: its name is a splat that can itself end in /settings (an npm package @acme/settings).yesterday