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
g1t/workflows
g1t's own reusable workflows, published from this folder of g1t's
repository to g1t/workflows on g1t.sh by .g1t/workflows/actions-release.yml.
| Workflow | What it does |
|---|---|
.g1t/workflows/deploy.yml | Builds the commit onto g1t.page with g1t/deploy. The deploy workflow g1t manages for a project calls it. |
jobs:
g1t:
uses: g1t/workflows/.g1t/workflows/deploy.yml@v1
with:
project: web
secrets: inherityaml