flagon-io/g1t

public

Where people and agents ship software together. The open-source git platform for the whole job: issues, agents, checks and deploys to the edge.

git agents cloudflare rust forge mcp

Merge branch 'socket-tickets'#124

How this runs on g1t · 27 notes

check: `actions/checkout` checks out from g1t.
plan: `actions/checkout` checks out from g1t.
plan: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
migrate: `actions/checkout` checks out from g1t.
migrate: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
core: `actions/checkout` checks out from g1t.
core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
core: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
edge: `actions/checkout` checks out from g1t.
edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
edge: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
front: `actions/checkout` checks out from g1t.
front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
front: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
smoke: `actions/checkout` checks out from g1t.

Triggered via push 14h ago

syntaqxc364520main

Status

Succeeded

Total duration

6m 48s

Artifacts

—

deploy.yml· on: push

Plansummary

Deploy plan for c364520

unit	stage	action	live	why
events	core		180b34a	nothing it is built from changed
identity	core		180b34a	nothing it is built from changed
repos	core		180b34a	nothing it is built from changed
work	core		180b34a	nothing it is built from changed
search	core		180b34a	nothing it is built from changed
projects	core		180b34a	nothing it is built from changed
chat	core		180b34a	nothing it is built from changed
docs-service	core		180b34a	nothing it is built from changed
notify	core		180b34a	nothing it is built from changed
agents	core		180b34a	nothing it is built from changed
billing	core		180b34a	nothing it is built from changed
integrations	core		180b34a	nothing it is built from changed
webhooks	core		180b34a	nothing it is built from changed
actions	core		180b34a	nothing it is built from changed
packages	core		180b34a	nothing it is built from changed
security	core		180b34a	nothing it is built from changed
deployments	core		180b34a	nothing it is built from changed
runner	core		180b34a	nothing it is built from changed
context	core		180b34a	nothing it is built from changed
og	core		180b34a	nothing it is built from changed
api	edge		180b34a	nothing it is built from changed
models	core		180b34a	nothing it is built from changed
pages	edge		4bc4681	nothing it is built from changed
status	edge		180b34a	nothing it is built from changed
web	front	deploy	180b34a	15 changed files (apps/web/app/components/chat/live.ts)
sudo	front		180b34a	nothing it is built from changed
docs	front	deploy	180b34a	1 changed file (apps/docs/src/content/docs/guides/authentication.md)