Skip to content
⌘K
Explore
Download
Docs
Sign in
Sign up
flagon-io
/
g1t
public
Star
0
Overview
Code
Issues
Pull requests
Workflows
Deployments
Insights
Files
Commits
Branches
Tags
Releases
Compare
52dfdb07b408a782ad05467d6188c835b4a54842
g1t
/
…
/
crates
/
rules
/
src
syntaqx
The smoke check looks for the landing page's Get started button: the page has said Get started instead of Start for free since 81a83931, so Deploy #248 failed its smoke on a landing page that was fine.
52dfdb0
yesterday
History
..
content.rs
glob.rs
legacy.rs
lib.rs
merge.rs
outcome.rs
push.rs
report.rs
select.rs
text.rs
validate.rs
window.rs
..
content.rs
Merge rulesets: branch and tag rules, agent-first, enforced on push and merge
6d ago
glob.rs
Merge rulesets: branch and tag rules, agent-first, enforced on push and merge
6d ago
legacy.rs
Merge rulesets: branch and tag rules, agent-first, enforced on push and merge
6d ago
lib.rs
Merge rulesets: branch and tag rules, agent-first, enforced on push and merge
6d ago
merge.rs
The contracts no longer describe g1t's own agents, and workspaces can keep their AI providers. Every consumer had already stopped using them, so the TypeScript and Rust contracts drop the workspace-agent, ability, look, skill-library, context, runner-agent and mention modules, the chat and docs RPCs agents posted and read through, the folio agent methods, the agent_waiting notification, agent.asked and memory.changed events, AI credit, token and gateway billing types, model routes and sessions, team agents, agent tokens, plan, review, message and confidence types, command rules, cost caps and confidence rules. The agents:run and models:* scopes are no longer offered by any preset, OAuth default or permission form, but a stored token or grant that names them still reads; and the removed operations are gone from the scope table, so the API's check that every operation has exactly one scope is strict again. What stored data needs in order to parse (old run and credential kinds, an agent team lead, retired rules and webhook events, old guardrail and integration settings) still parses, and a run's token is still PrincipalKind::Agent, which now means a run's token and the @g1t rows written before. The customize, marketplace, skills and claude-plugin contracts stay only until the mobile app drops its Customize screens.
yesterday
outcome.rs
Merge rulesets: branch and tag rules, agent-first, enforced on push and merge
6d ago
push.rs
Merge rulesets: branch and tag rules, agent-first, enforced on push and merge
6d ago
report.rs
Merge rulesets: branch and tag rules, agent-first, enforced on push and merge
6d ago
select.rs
The work, events, webhooks, actions, repos and packages services no longer run g1t's own agents. Work drops the 35 calls that queued issues for g1t, delegated them, messaged and reviewed through the agent, planned, captured memories automatically, rated confidence and capped agent spend, and its pull request lifecycle no longer revises or reviews: a pull request only advances to a merge by the repository's auto-merge setting. Merging a pull request that is behind now catches it up itself, through the repository's branch update, and lands it when the push arrives; when it can't be caught up cleanly the merge says to merge the base in and try again. Recording a session on a pull request, memory recall and remember, overlaps, the merge queue and required checks stay as they were.
yesterday
text.rs
Merge rulesets: branch and tag rules, agent-first, enforced on push and merge
6d ago
validate.rs
The contracts no longer describe g1t's own agents, and workspaces can keep their AI providers. Every consumer had already stopped using them, so the TypeScript and Rust contracts drop the workspace-agent, ability, look, skill-library, context, runner-agent and mention modules, the chat and docs RPCs agents posted and read through, the folio agent methods, the agent_waiting notification, agent.asked and memory.changed events, AI credit, token and gateway billing types, model routes and sessions, team agents, agent tokens, plan, review, message and confidence types, command rules, cost caps and confidence rules. The agents:run and models:* scopes are no longer offered by any preset, OAuth default or permission form, but a stored token or grant that names them still reads; and the removed operations are gone from the scope table, so the API's check that every operation has exactly one scope is strict again. What stored data needs in order to parse (old run and credential kinds, an agent team lead, retired rules and webhook events, old guardrail and integration settings) still parses, and a run's token is still PrincipalKind::Agent, which now means a run's token and the @g1t rows written before. The customize, marketplace, skills and claude-plugin contracts stay only until the mobile app drops its Customize screens.
yesterday
window.rs
Merge rulesets: branch and tag rules, agent-first, enforced on push and merge
6d ago
