Skip to content
Sign up

flagon-io/g1t

public
0

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
Deploy

A preview is live only while what it previews is: a branch's preview (one with no pull request) comes down when its branch is deleted, and the sweep takes down any whose branch is already gone. A pull request's preview has always come down when it closes or merges, but a branch's had nothing to take it down, so the previews that preview stacks built for another project's pull request, before projects stopped depending on each other (a9916137), stayed up and showed as a live Preview on projects with no pull requests at all, as flagon-io/automation-lab's v2 did. Moving a project no longer builds such a preview again (rebuildStack is gone with the stacks). A branch's preview from a project's deploy workflow stays while its branch is there, and one whose branches can't be read stays until they can. Checked: the deployments service's typecheck and its 88 tests (new: the sweep takes down a preview of a deleted branch and marks its deployment inactive while keeping a pull request's and a live branch's, and git.deleted takes a branch's preview down at once).#296

Download logs
How this runs on g1t · 32 notes
  • check: `actions/checkout` checks out from g1t.
  • check: `actions/cache/restore`: 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.
  • 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: `actions/cache/restore`: 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.
  • 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/restore`: 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/restore`: 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/restore`: 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/restore`: 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/restore`: 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/restore`: 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

syntaqxca321a8main

Status

Succeeded

Total duration

2m 3s

Artifacts

—

deploy.yml· on: push
Check42s
Plan35s
Migrations
core (ts)1m 0sg1t.sh
edge
front
Smoke10s
Plansummary

Deploy plan for ca321a8

unitstageactionlivewhy
eventscorecb3fedbnothing it is built from changed
identitycorecb3fedbnothing it is built from changed
reposcorecb3fedbnothing it is built from changed
workcorecb3fedbnothing it is built from changed
searchcorecb3fedbnothing it is built from changed
projectscorecb3fedbnothing it is built from changed
chatcorecb3fedbnothing it is built from changed
artifactscorecb3fedbnothing it is built from changed
telemetrycorecb3fedbnothing it is built from changed
notifycorecb3fedbnothing it is built from changed
billingcorecb3fedbnothing it is built from changed
integrationscorecb3fedbnothing it is built from changed
webhookscorecb3fedbnothing it is built from changed
actionscorecb3fedbnothing it is built from changed
packagescorecb3fedbnothing it is built from changed
securitycorecb3fedbnothing it is built from changed
deploymentscoredeploycb3fedb2 changed files (services/deployments/src/index.ts)
runnercorecb3fedbnothing it is built from changed
ogcorecb3fedbnothing it is built from changed
apiedgecb3fedbnothing it is built from changed
pagesedge5879548nothing it is built from changed
statusedgecb3fedbnothing it is built from changed
webfrontcb3fedbnothing it is built from changed
sudofrontcb3fedbnothing it is built from changed
docsfrontcb3fedbnothing it is built from changed