flagon-io/g1t

public

Git for AI scale: a forge for thousands of agents working on the same code at once.

Commit

Say why git over SSH is not on yet

It needs inbound TCP on port 22, which on Cloudflare means Workers inbound TCP, a beta g1t has applied for and is waiting on. HTTPS clones, fetches and pushes the same until then; SSH keys added in settings will be used once it is on.

syntaqxcommitted Parent5197201Browse files
3 files+14−40/3 viewed
+4−2
8787 - An event bus: every state change is published, logged and delivered to
8888 subscribers.
8989
90−Not built yet: git over SSH, a code-search index, and the Soon pages in
91−each project's menu. See the build order in the plan.
90+Not built yet: a code-search index and the Soon pages in each project's
91+menu. Git over SSH waits on inbound TCP on port 22, which on Cloudflare
92+means Workers inbound TCP, a beta g1t has applied for and is waiting on.
93+Use HTTPS until then. See the build order in the plan.
9294
9395 ## Try it
9496
+8−1
9494
9595 ## SSH
9696
97−Git over SSH is not available yet. Use HTTPS.
97+Git over SSH is not available yet. Use HTTPS, which works for clone,
98+fetch and push everywhere SSH would.
99+
100+Why: git over SSH needs raw TCP connections on port 22, and g1t runs
101+entirely on Cloudflare's network. Accepting inbound TCP traffic directly
102+into Workers is in a beta from Cloudflare that g1t has applied for and is
103+waiting on. SSH keys can already be added under **Settings → SSH keys**,
104+and will be used once SSH is on.
+2−1
2424 </TabsContent>
2525 <TabsContent value="ssh">
2626 <p className="rounded-lg border border-dashed border-line p-3 text-xs text-muted">
27− Git over SSH is not available yet. Use HTTPS for now.
27+ Git over SSH is waiting on inbound TCP on Cloudflare, which g1t has applied for. Use HTTPS for now: it
28+ clones, fetches and pushes the same. Keys you add under Settings will work as soon as SSH is on.
2829 </p>
2930 </TabsContent>
3031 <TabsContent value="agent">