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

Commit

The Home and Ask guides say how to ask g1t from Home (#52): Home opens with "What are we building today?" and a box that asks g1t, with its starters, and nothing in the guides said so. Home's guide gains Ask from Home (the box, Enter and Shift+Enter, the four starters and what each asks, answers kept in the direct message with @g1t, and a question left in the panel's box when Ask isn't set up or an answer is still coming), What changed (Summarize, the summary streamed onto the page, Ask a follow-up, Summarize again, In your direct message with g1t, the question as sent with the span's start in your zone, the card starting over on another span, and what owners and members are told when Ask isn't set up), and Explain a change on every Landed row with what it asks for a merge or push, a build, a release or a package. Where you're needed now names each row's button, and says a pull request ready to merge says Open, since it opens the pull request where you merge it; Start here says its title links to what it picked, its fields (Owner, Next, Waiting, At stake, Why this one), and that its button says Open pull request for a pull request and names the action otherwise. Ask's guide gains Ask from Home, so the panel's side says which Home questions open it and which answer on the page. The notifications guide called Home's list Needs you; it is Where you're needed.

Checked:
every label and question against apps/web/app/components/home-ask.tsx, home-summary.tsx, home.tsx (NeedItem, StartHere, ExplainButton), routes/workspace/home.tsx (card order), lib/home.ts (HOME_STARTERS, summarizeQuestion, explainQuestion, codeRow and the notification and chat rows' labels, WHY), lib/ask.ts and ask-button.tsx / ask-composer.tsx (a queued question sent only when Ask is ready and not answering, else left in the box); the docs build, with the new anchors present.
G1t-Session:
ses_01m4ynr1peevvs8zwaqakycv2e
syntaqxcommitted Parent2e90f6fBrowse files
3 files+117−100/3 viewed
+19−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+## Ask from Home
171+
172+[Home](/guides/home/#ask-from-home) asks g1t for you in three places, all
173+in the same conversation as the panel:
174+
175+- **The box at the top**, under **What are we building today?**, and its
176+ starters (**What needs me first?**, **What shipped today?**, **Who's
177+ working on what?**). What you send there opens the Ask panel and is
178+ sent as if you had typed it in the panel.
179+- **Explain**, on each row of **Landed**, asks what that one change did,
180+ why, and whether it is live, in the panel.
181+- **Summarize**, on **What changed**, writes g1t's plain-English summary
182+ of the span on Home itself, rather than in the panel. **Ask a
183+ follow-up** under it opens the panel on the same conversation.
184+
185+When Ask is not set up yet, or g1t is still answering an earlier
186+question, the panel opens with the question in its box instead of
187+sending it; send it once it can be answered.
188+
170189 ## One conversation, in Ask and in Chat
171190
172191 Ask is your **direct message with @g1t** in [Chat](/guides/chat/#talk-with-g1t).
+96−9
11 ---
22 title: Home
3−description: Your workspace's front page. Where you're needed now, what happened since you were last here, what is running, and the one item to start with. How every number is worked out.
3+description: Your workspace's front page. Ask g1t what to do, where you're needed now, what happened since you were last here in plain English, what is running, and the one item to start with. How every number is worked out.
44 ---
55
66 **Home** is the first page of your workspace, at `/<workspace>/-/home`.
7−It answers three questions, in this order:
7+It opens with **What are we building today?** and a box that
8+[asks g1t](#ask-from-home), then answers three questions, in this order:
89
910 1. **Where you're needed**: everything waiting on you, however long ago
1011 it started, with the action beside each item.
11−2. **What happened while you were away**: what settled by itself and
12− what went live; what people did; what landed; deploys and spend,
13− since you were last here.
12+2. **What happened while you were away**: what changed, in plain
13+ English when you ask for it; what settled by itself and what went
14+ live; what people did; what landed; deploys and spend, since you were
15+ last here.
1416 3. **What is running now**: workflow runs and builds still going.
1517
1618 **Start here** picks the one item to do first.
2123
2224 Every number on the page comes from what g1t has recorded. Nothing is
2325 estimated. When a part of g1t does not answer, the section it feeds says
24−so, and the rest of the page still shows.
26+so, and the rest of the page still shows. Only what you ask g1t is written
27+by a model: [What changed](#what-changed) and the answers in Ask.
28+
29+## Ask from Home
2530
31+The box at the top asks g1t anything about your work. Type a question and
32+press **Enter** (**Shift+Enter** starts a new line): the top bar's
33+[Ask](/guides/ask/) panel opens and sends it, and the answer streams in
34+there. Under the box are questions to start with:
35+
36+| Starter | What it does |
37+| --- | --- |
38+| **Summarize what changed since I was last here** | Writes a summary of the span into [What changed](#what-changed), further down the page, and brings it into view. Over another span it says so, such as **Summarize what changed in the last 7 days** |
39+| **What needs me first?** | Asks which things need you, most urgent first, one line each on what to do |
40+| **What shipped today?** | Asks what shipped today: what is live, what is still deploying, and what failed |
41+| **Who's working on what?** | Asks who is working on what right now, and whether anything is stuck |
42+
43+Everything you ask from Home goes to your
44+[direct message with @g1t](/guides/ask/#one-conversation-in-ask-and-in-chat),
45+as a question asked in Ask does, so you can carry on from it in Ask or in
46+Chat. It answers with your workspace's own AI provider, so an owner has to
47+[set Ask up](/guides/ask/#set-it-up) first. Until then, or while g1t is
48+still answering an earlier question, the panel opens with your question
49+in its box rather than sending it, so nothing you typed is lost.
50+
2651 ## Where you're needed
2752
2853 This list has no time window: something that started waiting a week ago
3863 A notification about something already on the list, such as a pull
3964 request whose row is there, is left out.
4065
66+Each row's button takes you to the place where you act on it: **See the
67+build** for a failed production build, **Review** for a review asked of
68+you, **Respond** for an invitation, **Look** for a job waiting for a
69+runner or your pull request that can't land (**Review** when it waits
70+for a verdict), **Reply** for a message, and
71+**Open** for a notification. Your pull request that is ready to merge,
72+marked **Ready to merge**, says **Open** too: it opens the pull request,
73+where you merge it. Nothing on Home merges on the spot.
74+
4175 Rows are ordered most pressing first, by tier, then by how long each has
4276 waited, longest first:
4377
5791 **Start here** is the first row of Where you're needed: the most pressing
5892 tier, and within it the row that has waited longest. g1t picks it with
5993 that rule, so the same rows always give the same pick.
60−The card shows who is on it, the next action, how long it has waited, what
61−is at stake, and why it was picked.
94+The card shows who is on it (**Owner**), the step it waits for (**Next**,
95+such as **Merge** or **Review**), how long it has waited (**Waiting**),
96+what is at stake (**At stake**), and **Why this one**, such as
97+"Everything it needs is met; it lands when you merge it." When others in
98+its tier are waiting too, it adds that this one has waited longest.
6299
100+Its title links to what it picked: the pull request, issue or build. The
101+button under it opens the same place. For a pull request (one ready to
102+merge, a review asked of you, or yours that is stuck) it says **Open pull
103+request**; you merge or review there. For anything else it names the
104+action, such as **See the build** or **Respond**.
105+
63106 ## Since you were last here
64107
65108 Home remembers when you were last on it, for each workspace, with your
104147 When Code and Chat both failed to answer, the sentence ends with "what
105148 people did couldn't be read" rather than reading as quiet.
106149
150+### What changed
151+
152+The first card, **What changed**, has g1t tell you what happened in the
153+span in plain English: what changed, why, and what is live. It is not
154+written until you ask, since each summary is a call to your workspace's
155+AI provider:
156+
157+1. Choose **Summarize** on the card, or the
158+ [starter](#ask-from-home) **Summarize what changed since I was last
159+ here** at the top of the page.
160+2. g1t's summary streams into the card as it is written. It reads g1t as
161+ you, as [Ask](/guides/ask/#what-it-can-read) does, so it covers only
162+ what you can see.
163+3. When it is finished:
164+ - **Ask a follow-up** opens the top bar's Ask on the same
165+ conversation, so you can ask about anything in the summary.
166+ - **Summarize again** writes a new one.
167+ - **In your direct message with g1t** opens the conversation in Chat,
168+ where the summary is kept.
169+
170+The question g1t is sent reads as you would ask it, with the span's start
171+in your time zone: "Summarize what changed since I was last here (2:12
172+PM) in plain English." Choosing another span with the switch starts the
173+card over. When Ask is not set up, the card says so: owners get a link to
174+connect a provider and choose it for Ask, and members are told to ask an
175+owner.
176+
107177 ### While you were away
108178
109−The first card says what finished by itself in the span, and what is
179+The next card says what finished by itself in the span, and what is
110180 live. (Over **Last 24 hours** and **Last 7 days** it is called **Settled
111181 for you**.) Its first line counts:
112182
162232 grouped by day (**Today**, **Yesterday**, **Sun, Oct 11**), five of each
163233 day showing.
164234
235+#### Explain a change
236+
237+Every row has an **Explain** button (the sparkle beside its time,
238+"Explain this change in plain English"). It opens the top bar's
239+[Ask](/guides/ask/) and asks g1t about that one change:
240+
241+| Row | What g1t is asked |
242+| --- | --- |
243+| A merge or a push | "Explain pull request #47 in acme/web in plain English: what changed, why, and is it live?" (or the commit, for a push) |
244+| A production build | What went out in that deployment |
245+| A release or a package version | What's new in it |
246+
247+The answer is kept in your direct message with @g1t, like everything you
248+[ask from Home](#ask-from-home).
249+
165250 #### Live after merge
166251
167252 Each merge and push says whether it is live yet, for a project that
255340 deployments or sessions can't be read, Landed shows its rows without
256341 their live labels or agent markers.
257342 - While you were away says when your notifications can't be read.
343+- What changed says when Ask can't be reached or isn't set up, or when
344+ the question could not be sent.
258345 - If your last visit can't be read, the span is the last 24 hours and the
259346 page says why.
260347
+2−1
9898 A thread that leaves you nothing to do moves to Done by itself, read, the
9999 moment what it told you of is over: a later run passes, the pull request
100100 merges, the review is no longer asked of you. It leaves your unread count,
101−the bell, [Home](/guides/home/)'s **Needs you** and `g1t status`, and
101+the bell, [Home](/guides/home/#where-youre-needed)'s **Where you're
102+needed** and `g1t status`, and
102103 stays under **Done** with its history. New activity brings it back, as with
103104 any thread.
104105

Comments

Sign in to comment.