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
Deploy

An open pull request's page no longer asks repos whether it is behind a second time, and anyone's ready pull request says it is ready to merge. Signed in, flagon-io/g1t #41 took 5 to 10 seconds and once failed: get_pull worked out whether it is behind (stored with its mergeability for its head, as merge_choices does), then the merge gate asked repos `behind` again on every view, a walk of the git store that took up to 5 s (Workers Logs: /rpc/behind 4.9 s, 649 ms CPU). The gate now takes what the page already worked out (merge_gate_seen), as does the lifecycle's own gate; merging and the queue still ask repos as they did. And the lifecycle was worked out only for pull requests g1t's agent made (managed = 1), which since g1t stopped running agents of its own is none, so a person's pull request that met everything its branch asks for (#41: CI passed, no approvals required) said nothing about being ready. Every open pull request now gets one; only one g1t manages merges by itself (auto_merge is gated on managed), and anyone else's draft still gets none, so its page does not keep refreshing. Lists keep showing a lifecycle only for managed pull requests, since nothing yet refreshes a stored one for the rest. Checked: cargo test -p g1t-work (189 passing).#330

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

syntaqx6e24edfmain

Status

Succeeded

Total duration

7m 47s

Artifacts

—

deploy.yml· on: push
Check50s
Plan46s
Migrations
core (rust)3m 4sg1t.sh
edge
front (web)3m 14sg1t.sh
Smoke17s
Plansummary

Deploy plan for 6e24edf

unitstageactionlivewhy
eventscore8e1a370nothing it is built from changed
identitycore8e1a370nothing it is built from changed
reposcore8e1a370nothing it is built from changed
workcoredeploye446ed43 changed files (services/work/src/lib.rs)
searchcore8e1a370nothing it is built from changed
projectscore8e1a370nothing it is built from changed
chatcore8e1a370nothing it is built from changed
artifactscore8e1a370nothing it is built from changed
telemetrycore8e1a370nothing it is built from changed
notifycore8e1a370nothing it is built from changed
billingcore8e1a370nothing it is built from changed
integrationscorea80666bnothing it is built from changed
webhookscore8e1a370nothing it is built from changed
actionscore8e1a370nothing it is built from changed
packagescore8e1a370nothing it is built from changed
securitycore8e1a370nothing it is built from changed
deploymentscore8e1a370nothing it is built from changed
runnercorea80666bnothing it is built from changed
ogcore8e1a370nothing it is built from changed
apiedge8e1a370nothing it is built from changed
pagesedge2a24415nothing it is built from changed
statusedge8e1a370nothing it is built from changed
webfrontdeploye446ed41 changed file (apps/web/app/routes/workspace/ai.tsx)
sudofront8e1a370nothing it is built from changed
docsfronta80666bnothing it is built from changed
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             1.136 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