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.

Star 0

git agents cloudflare rust forge mcp

Deploy

Overview: Recent changes show the avatar of whoever the line names, and every name opens its card#96

Download logs

How this runs on g1t · 26 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.

Triggered via push 13h ago

syntaqxf3acccemain

Status

Succeeded

Total duration

6m 50s

Artifacts

—

deploy.yml· on: push

front (web)2m 4s g1t.sh

Plansummary

Deploy plan for f3accce

unit	stage	action	live	why
events	core		0611189	nothing it is built from changed
identity	core		0611189	nothing it is built from changed
repos	core		1315c25	nothing it is built from changed
work	core		0bd8603	nothing it is built from changed
search	core		0611189	nothing it is built from changed
projects	core		0611189	nothing it is built from changed
billing	core		0611189	nothing it is built from changed
integrations	core		0611189	nothing it is built from changed
webhooks	core		0611189	nothing it is built from changed
actions	core		0611189	nothing it is built from changed
packages	core		0611189	nothing it is built from changed
security	core		0611189	nothing it is built from changed
deployments	core		0611189	nothing it is built from changed
runner	core		0611189	nothing it is built from changed
context	core		0611189	nothing it is built from changed
og	core		0611189	nothing it is built from changed
api	edge		0611189	nothing it is built from changed
models	edge		0611189	nothing it is built from changed
pages	edge		61ffc80	nothing it is built from changed
status	edge		0611189	nothing it is built from changed
web	front	deploy	1315c25	1 changed file (apps/web/app/routes/repo/overview.tsx)
sudo	front		0bd8603	nothing it is built from changed
docs	front		1315c25	nothing it is built from changed