Skip to content
Sign up

flagon-io/g1t

public
00

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
syntaqxA pushed annotated tag starts the workflows that filter its tags: pushing cli-v0.3.5 and then cli-v0.3.6 (alone, git push g1t cli-v0.3.6) to flagon-io/g1t started no CLI release run from .g1t/workflows/cli-release.yml (push: tags: ["cli-v*"]), while cli-v0.3.3 and cli-v0.3.4 had started runs #4 and #5. Those two were lightweight tags; 0.3.5 and 0.3.6 are annotated. After a push, repos checks each pushed ref against where the store actually has it (the store can refuse one ref and accept another) and announces only refs that moved; for a tag it compared the commit the tag reads back as with the hash the push named, which for an annotated tag is the tag object (accae3e8), never the commit it leads to (42a29574), so the tag was taken as refused and no git.push event was published: Actions never heard of it, and nothing about the tag's commit already having run on main was involved. That check now lives in pushed.rs (pushed_to): a branch must be at the commit pushed, as before; a tag whose commit differs from what the push named is taken as pushed unless what it named is itself a commit (then the store left a lightweight tag elsewhere), and a tag is announced at the commit it leads to, as git.push says its after is, so the run is at that commit, as GitHub runs a tag push at the tagged commit. A tag the store cannot read back is still taken as pushed. Deploy: repos. Checked: cargo test -p g1t-repos (367, with new tests for an annotated tag, a lightweight one the store left elsewhere and branches); cargo check -p g1t-repos --target wasm32-unknown-unknown.

README.md

g1t/deploy

Builds the checkout a g1t Actions job is in and puts it on g1t.page: production when the run is on the project's production branch, the pull request's preview for a pull request's run, and the branch's preview for a run on any other branch.

name: Deploy

on:
  push:
    branches: [main]
  pull_request:

permissions:
  contents: read
  deployments: write

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - id: deploy
        uses: g1t/deploy@v1
      - run: echo "Live at ${{ steps.deploy.outputs.url }}"
yaml

The project must have Deployments on, and the workspace's plan must include them. The guide, Deploying from a workflow, says what is built and when.

Inputs

InputDefault
projectThe repository's one project with Deployments onThe project's slug. Needed when the repository has several.
root-dirThe project's settingWhere the project is in the checkout.
build-commandThe project's setting, else what the build findsWhat builds it.
output-dirThe project's setting, else the folder the framework writes, else the first of dist, build, out, public, _site, .output/publicThe folder a static build writes.
build-asThe project's setting, else autoWhat it is built as: auto, static, workers or docker. A container is built with the docker on the job's PATH.
dockerfileThe project's setting, else Dockerfile or ContainerfileThe Dockerfile a container is built from, relative to the project.
shaThe run's commitThe commit this is a build of, for its g1t / deploy check.
token${{ github.token }}The job's own token. It needs deployments: write; any other token is refused.

Outputs

Output
urlWhere the app is served.
deployment-idThe build's id, dpl_….
kindproduction or preview.

How it works

  1. It calls POST /repos/{owner}/{repo}/deployments/builds with the job's token. g1t checks the plan and the spend limit, decides production or preview from the run, sets the commit's g1t / deploy check to pending, and answers with a token for this build alone and the project's variables and secrets for builds of that kind.
  2. It masks that token and every secret with ::add-mask::.
  3. It runs g1t-runner deploy in the checkout, which installs, builds and uploads the app exactly as g1t's own builds do, and reports to g1t with the build's token. The build's log is in the step's.

A pull request from a fork or from someone without the Write role, and a run that had to be approved, build without the project's secrets. The build's time is the job's Actions time; it is not charged again.

g1t-runner is on g1t's machines. Elsewhere (a self-hosted runner), the action uses the one on PATH, or downloads the newest release from https://g1t.sh/downloads/runner/latest/ and checks it against the release's SHA256SUMS. It runs on Linux and macOS, with curl and either jq or python3.