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.

g1t.sh
gitagentscloudflarerustforgemcp

Commit

The Ask guide says how Ask builds something new from one card, and the build-and-ship guide points to it (#52). Since 2a5bee50 (#53), asked to build something with no repository yet, Ask proposes a session for a new one; starting it creates the repository as you, turns on its deployments (g1t plan and Admin, or Not deployed: and why), opens the issue and starts the session, which pushes the first version to the default branch and watches it go live. Ask's guide gains Building something new with the card's words (Build "…" in …, Created, Live once the first version is pushed at); build-and-ship's Ask g1t only reads becomes Or start from Ask, and its table says turning deployments on is also done by starting that card. Ask itself still changes nothing. Checked: proposalSteps and proposalTitle in apps/web/app/lib/ask.ts, the card in components/ask-steps.tsx, 2a5bee50's message; the docs build, and the link crawler (0 misses).

Closes #52

G1t-Session:
ses_01m4ynr1peevvs8zwaqakycv2e
syntaqxcommitted Parent16d2bddBrowse files
ClosedDocs and marketing pass #52
2 files+43−70/2 viewed
+33−0
167167 Ask can tell you where it stands. If a session already holds the issue, Ask
168168 links it rather than proposing another.
169169
170+### Building something new
171+
172+Ask for something that has no repository yet, such as "build a status page
173+for our API", and the card proposes a new one in your workspace: **Build
174+"Status page" in acme/status-page**. Under its title it says what starting
175+it does, for example "Creates the private repository, turns on its
176+deployments, then runs in your own harness and pushes the first version,
177+which goes live on g1t.page." The repository is public only if you ask for
178+that, and deployments are left off if you ask for that too.
179+
180+Choosing **Start session** or **Copy Claude Code command**:
181+
182+1. Creates the repository as you, with the issue's title as its project's
183+ description.
184+2. Turns on its [deployments](/guides/deployments/). This needs the
185+ workspace on the g1t plan and the Admin role on the repository, which
186+ you have as its creator. If it can't, the card says **Not deployed:**
187+ and why, and the session still builds the app.
188+3. Opens the issue and starts the session.
189+
190+The card then shows **Created** with a link to the repository, and **Live
191+once the first version is pushed at** its production address on
192+g1t.page. The session pushes its first working version straight to the
193+default branch, since an empty repository has nothing to open a pull
194+request against, closes the issue, and watches `g1t deploy list` until
195+production is live, ending its report with the address. Every change after
196+that goes through pull requests as usual. Choosing the card again, or Copy
197+after Start, uses the repository it already made.
198+
199+Ask itself still changes nothing: your click on the card does. For a
200+repository that already exists, deployments are turned on in its
201+**Settings → Deployments**.
202+
170203 ## Ask from Home
171204
172205 [Home](/guides/home/#ask-from-home) asks g1t for you in three places, all
+10−7
209209 | Approve its own pull request | No | Someone else approves | |
210210 | Read deployments, logs and errors | Yes | `g1t deploy list` and `g1t logs`, or `workflow` `list_deployments` and `observability` | `deployments:read`, `observability:read` |
211211 | Start the g1t plan | No | An owner, under **Settings → Billing and plans** | |
212−| Turn deployments on or off, or change their settings | No | You, under the project's **Settings → Deployments**, with the Admin role | |
212+| Turn deployments on or off, or change their settings | No | You, under the project's **Settings → Deployments**, with the Admin role, or by starting [Ask's card for a new repository](/guides/ask/#building-something-new) | |
213213 | Build production again | No | **Redeploy** on the project's overview, with the Write role, or a push to the default branch | |
214214
215215 Scopes are explained under [scopes](/guides/authentication/#scopes);
216216 [MCP tools](/reference/mcp/) and the [CLI reference](/reference/cli/) list
217217 every action and command.
218218
219−## Ask g1t only reads
219+## Or start from Ask
220220
221−[Ask](/guides/ask/), and `@g1t` in Chat, reads g1t as you with read-only
222−access: it cannot create a repository, push, merge or deploy. Asked to do
223−work, it proposes a session in your own harness instead, with **Start
224−session** or **Copy Claude Code command**; see
225−[Asking for work](/guides/ask/#asking-for-work).
221+[Ask](/guides/ask/), and `@g1t` in Chat, reads g1t as you and changes
222+nothing itself: it cannot push, merge or deploy. Ask it to build something
223+that has no repository yet, though, and it proposes a session for a new
224+one. When you choose **Start session** or **Copy Claude Code command** on
225+that card, your click creates the repository, turns on its deployments
226+(with the g1t plan), opens the issue and starts the session, which pushes
227+the first version and watches it go live. See
228+[Building something new](/guides/ask/#building-something-new).

Comments

Sign in to comment.