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
syntaqxAgents are told how a commit closes an issue: on flagon-io/g1t #47 the billing session pushed its work straight to main with commits ending "(#47)", which only links the issue, so #47 stayed open after it shipped and was closed by hand. The plugin's SessionStart and subagent context (TRAILER in hooks/g1t.mjs), the work-on-issue skill's Finish step, the system prompt of sessions on Claude Managed Agents (for a repository's first commit) and the MCP server's instructions now say that a pull request's merge closes its issue, and a commit pushed straight to the default branch closes one only when its message says Closes #N (Fixes, Resolves), never with a bare (#N); the MCP instructions add that issue close with commit closes one after the fact. The Claude Code plugin guide says so. Deploy: api and integrations; the plugin ships with its next release. Checked: node --test of plugins/claude-code/test (56), cargo test -p g1t-api mcp (5), cargo test -p g1t-integrations agent_sessions (11).

README.md

GitHub's workflow schema

workflow-v1.0.json is GitHub's schema for workflow files, copied unchanged from actions/languageservices, file workflow-parser/src/workflow-v1.0.json, at commit 4043eda158e16579cc5fb1b0b07a4bce2a76f0b5 (5 August 2026). It is MIT licensed; LICENSE is that repository's licence, copied from the same commit.

g1t does not read it at run time. src/syntax.rs lists the keys each part of a workflow may have, and its tests check those lists against this file, so they cannot drift from GitHub's. To update it, copy the file again, write the commit here, and run cargo test -p g1t-actions.