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 pull request's merge options are read from what work keeps, not from the git store. GET /repos/flagon-io/g1t/pulls/41/merge-options took 8.0 to 8.6 s every time: merge_choices made the default merge messages from the branch's commits, and asked repos inspect_commits for them on every call, uncached. That call read the source's and the base's histories (1,000 commits each), worked out the merge base, fetched a pack from the git store and parsed it, asked identity who owns each signing key and address, and, for each of up to 250 commits, read its parent's tree and every changed level of both trees to list its files: all of it for messages that use only each commit's message and author. The site's stream gives up after 5 s, so the merge box never got its real choices and stayed on the settings-only box.

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.

WorkflowWhat it does
.g1t/workflows/deploy.ymlBuilds 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