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

syntaqxA deploy build reads g1t's reason when a step is refused: ureq makes any status over 399 an error, so the registry step's 409 not_enabled (g1t.page runs no containers yet) failed the build as "could not report registry to g1t: status code 409" before the build could fall back to the project's site, or say Docker deployments are not switched on. Tests answer a step with a 409 and a 502.998eca2yesterdayHistory

..
.g1t
README.md

README.md

g1t/workflows

g1t's own reusable workflows, published from this folder of g1t's repository to g1t/workflows on g1t.sh by .g1t/workflows/actions-release.yml.

Workflow	What it does
`.g1t/workflows/deploy.yml`	Builds the commit onto g1t.page with `g1t/deploy`. The deploy workflow g1t manages for a project calls it.

jobs:
  g1t:
    uses: g1t/workflows/.g1t/workflows/deploy.yml@v1
    with:
      project: web
    secrets: inherit

yaml