Skip to content
⌘K
Explore
Download
Docs
Sign in
Sign up
flagon-io
/
g1t
public
Star
0
Overview
Code
Issues
Pull requests
Agents
Workflows
Deployments
Insights
Files
Commits
Branches
Tags
Releases
Compare
b29a7e4c1bcac94bf62c23db2c9648bb835acff6
g1t
/
crates
/
contracts
syntaqx
The rail itself ships with the navigation it was committed without: the file that draws it was renamed from the dock and left out of the last change.
b29a7e4
1d ago
History
src
Cargo.toml
src
Home says what people did as well as what agents did. Since you were last here now has a People column and an Agents column: who pushed how many commits to which projects, pull requests opened, merged and reviewed, issues opened and closed, docs edited, messages sent and deploys that went out, each line a link to where those are listed, with the agents' acceptance (first time, after review, didn't finish) kept as a row of their column; the sentence under the heading sums it up honestly, and says when a part of g1t could not be read, or that the span was quiet. Landed counts merged pull requests, commits pushed straight to a default branch, production deploys that went live, releases and packages, newest first; Running now adds workflow runs. Behind it, the events service answers an activity digest over a span in one round trip from its existing indexes, every push now records how many commits it carried, and chat counts the messages sent in the conversations you can read. The Home guide defines every line, and says how this scales.
1d ago
Cargo.toml
API and MCP server, Rust identity service, registration, site redesign
10d ago
