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

Every install in g1t's workflows and deploy tool goes through scripts/deploy/npm-ci.mjs, which runs npm ci again when a connection drops: npm does not retry a body that breaks off midway, so an ECONNRESET or network aborted, an install that ends without saying why, or one that prints nothing for 12 minutes is tried again, up to three times; a real error, such as a lockfile out of step, still fails at once. A test keeps every workflow on it.#257

Download logs
How this runs on g1t · 36 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.
  • npm-cache: `actions/checkout` checks out from g1t.
  • npm-cache: `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.
  • npm-cache: `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.
  • npm-cache: `actions/cache/save`: 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`: 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`: 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`: 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

syntaqx576db88main

Status

Failed

Total duration

31m 13s

Artifacts

—

deploy.yml· on: push
Check59s
npm's downloads14s
Plan37s
Migrations
core (ts)30m 10sg1t.sh
edge
front
Smoke
Plansummary

Deploy plan for 576db88

unitstageactionlivewhy
eventscoredb52129nothing it is built from changed
identitycoredb52129nothing it is built from changed
reposcoredb52129nothing it is built from changed
workcoredb52129nothing it is built from changed
searchcoredb52129nothing it is built from changed
projectscoredb52129nothing it is built from changed
chatcoredb52129nothing it is built from changed
artifactscoredb52129nothing it is built from changed
telemetrycoredb52129nothing it is built from changed
notifycoredb52129nothing it is built from changed
billingcoredb52129nothing it is built from changed
integrationscoredb52129nothing it is built from changed
webhookscoredb52129nothing it is built from changed
actionscoredb52129nothing it is built from changed
packagescoredb52129nothing it is built from changed
securitycoredb52129nothing it is built from changed
deploymentscoredb52129nothing it is built from changed
runnercoredeploydb521292 changed files (services/runner/src/forward.test.ts)
ogcoredb52129nothing it is built from changed
apiedgedb52129nothing it is built from changed
pagesedge5879548nothing it is built from changed
statusedgedb52129nothing it is built from changed
webfrontf776feanothing it is built from changed
sudofrontf776feanothing it is built from changed
docsfrontdeployf776fea1 changed file (apps/docs/src/content/docs/guides/actions.md)