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
syntaqxSix-digit codes are typed into six boxes: the sign-in's second step, turning two-factor on or off in settings, and confirming an email address. It is shadcn's Input OTP (components/ui/input-otp.tsx, on input-otp 1.4.2) in g1t's tokens: two groups of three with a rule between, the current box ringed in lavender with a blinking caret (still under reduced motion), every box red when the code was refused. One real input sits under the boxes with the field's id, name="code" and autocomplete="one-time-code", so password managers and phones' code suggestions fill it and the form posts what it did before. A pasted "123 456" or "123-456" lands as six digits. On sign-in and email confirmation the form is sent as soon as the sixth digit is in, and a refused code is cleared and the boxes focused for the next. Where a recovery code is also taken (signing in, turning two-factor off), "Use a recovery code" switches to the text field, and a recovery code pasted into the boxes switches by itself with the code carried across, so one is never cut to digits (lib/otp.ts looksLikeRecoveryCode, codeDigits). components/one-time-code.tsx holds CodeSlots and TwoFactorCodeField. Checked: apps/web tsc -b and npm test (993; new: pasted codes and telling a recovery code apart; the confirm page's field test reads the boxes), and the fields rendered alone in headless Chrome driven over CDP: focus on load, typing 123456 submitted 123456, pasting "987 654" gave 987654 and submitted, pasting k7m2q-9xw4d into the boxes moved it whole to the Recovery code field. Not tried with a real password manager or on a phone.

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.