syntaqxSessions g1t starts on Claude Managed Agents can push a new repository's first version: on flagon-io/demo #1 the session built the page, then its `git commit && git push origin main` was blocked by the sandbox's permission check (permission_policy auto), so nothing went live. Two things made it look unsafe. The kickoff, the only user turn, said "make the change on a branch, open a draft pull request" and called the issue reference material, so nothing the person wrote asked for a push to the default branch (Ask's new-repository card says so in its instruction; a session started by @g1t in a comment didn't). And the agent set its own identity, `git -c user.name=syntaqx -c user.email=…`, to commit as the person. The kickoff's implement step now says that when the repository has no commits yet there is nothing to open a pull request against, so the first version goes straight to the default branch, and that this push is asked of it. The setup command sets git's user.name and user.email to the person who started the session (their username and noreply address), and the system prompt says never to set another author. The sessions guide says both. Checked: cargo test -p g1t-integrations (76), wasm32 check of g1t-integrations.cf8330cHistory
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.