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.

g1t.sh
gitagentscloudflarerustforgemcp
Deploy

Ask's card remembers what it did, step by step, on the answer that proposed it (#53): the card kept its progress only in the page that clicked it, so back in Chat the same answer offered Start session again, and a second click on the new-repository card opened a second issue and started a second session on the same empty repository (flagon-io/ask-hello-test got #1 and #2, each with a session racing to push the first version). What a click does is now kept on the @g1t answer as it happens, in a proposal_state step beside the proposal: chat's new g1t_proposal merges it in (the viewer's own direct message with g1t only, known fields only) and tells the room, so every open copy of the answer updates. The card starts from it wherever the answer is read: Created with the repository, Live once the first version is pushed at with the address or Not deployed: with why, and Started with its links. Another click carries on from there rather than over: a session already started is shown, not started again; a repository already made, its deployments and the issue already opened are used; and while a click is still starting it (90 seconds at most), another says it's already starting. A failed step clears that hold so a retry works. Ask's steps also stop marking a read that found nothing as not read: checking that a new repository's name is free answers "not found", which showed as 1 not read on every new-repository answer.#367

Download logs
How this runs on g1t · 32 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.
  • 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/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: `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/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: `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/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: `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

syntaqx304b02cmain

Status

Succeeded

Total duration

9m 10s

Artifacts

—

deploy.yml· on: push
Check46s
Plan39s
Migrations
g1t.sh
edge (ts)1m 36sg1t.sh
g1t.sh
Smoke21s
Plansummary

Deploy plan for 304b02c

unitstageactionlivewhy
eventscore89ee2f7nothing it is built from changed
identitycore89ee2f7nothing it is built from changed
reposcore89ee2f7nothing it is built from changed
workcore89ee2f7nothing it is built from changed
searchcore89ee2f7nothing it is built from changed
projectscoredeploy89ee2f71 changed file (packages/contracts/src/chat.ts via packages/contracts)
chatcoredeploy89ee2f74 changed files (services/chat/src/g1t.test.ts)
artifactscoredeploy89ee2f71 changed file (packages/contracts/src/chat.ts via packages/contracts)
telemetrycoredeploy89ee2f71 changed file (packages/contracts/src/chat.ts via packages/contracts)
notifycoredeploy89ee2f71 changed file (packages/contracts/src/chat.ts via packages/contracts)
billingcore89ee2f7nothing it is built from changed
integrationscoredeploy89ee2f72 changed files (services/integrations/src/ask_loop.rs)
webhookscore89ee2f7nothing it is built from changed
actionscore89ee2f7nothing it is built from changed
packagescore89ee2f7nothing it is built from changed
securitycore89ee2f7nothing it is built from changed
deploymentscoredeploy89ee2f71 changed file (packages/contracts/src/chat.ts via packages/contracts)
runnercoredeploy89ee2f71 changed file (packages/contracts/src/chat.ts via packages/contracts)
ogcoredeploy89ee2f71 changed file (packages/contracts/src/chat.ts via packages/contracts)
apiedge89ee2f7nothing it is built from changed
pagesedge2a24415nothing it is built from changed
statusedgedeploy89ee2f71 changed file (packages/contracts/src/chat.ts via packages/contracts)
webfrontdeploy89ee2f711 changed files (apps/web/app/components/ask-steps.tsx)
sudofrontdeploy89ee2f71 changed file (packages/contracts/src/chat.ts via packages/contracts)
docsfrontdeploy89ee2f73 changed files (apps/docs/src/content/docs/guides/ask.md)
core (rust)summary

sccache

Compile requests                       8
Compile requests executed              3
Cache hits                             3
Cache hits (Rust)                      3
Cache misses                           0
Cache hits rate                   100.00 %
Cache hits rate (Rust)            100.00 %
Cache timeouts                         0
Cache read errors                      0
Forced recaches                        0
Cache write errors                     0
Cache errors                           0
Compilations                           0
Compilation failures                   0
Non-cacheable compilations             0
Non-cacheable calls                    5
Non-compilation calls                  0
Unsupported compiler calls             0
Average cache write                0.000 s
Average compiler                   0.000 s
Average cache read hit             0.760 s
Failed distributed compilations        0

Non-cacheable reasons:
-                                      2
missing input                          2
crate-type                             1

Cache location                  ghac, name: sccache-v0.18.0, prefix: /sccache/
Base directories                (none)
Version (client)                0.18.0