Ship the code.
Docs follow.
Connect your repositories once. When a pull request merges, Thally analyzes the change, drafts the documentation updates it implies, and opens them as a pull request on your docs repo, ready for your review.
Read-only GitHub App. Nothing publishes until a human approves it.
Trusted by the AI tools your readers already use
DEFAULT_TIMEOUT_MS 30000 to 60000
pull_request.closed · merged on the watched default branch
/sdk/configuration
Default timeout documented at 30 seconds.
/guides/quickstart
Evidence says nothing to update here.
Approve and merge
Nothing publishes until a human approves it.
Thally analyzes the change
The Content Graph matches the diff to affected docs.
docs: default timeout is now 60s
Opened by thally-bot · needs 1 review
/sdk/configuration updated
/guides/long-running-jobs updated
Changelog entry drafted
Draft release note
Timeout change, retries, and defaults.
Set it up once. It runs on every merge.
You choose the events · Thally ignores the rest
docs: document the new request timeout
@@ guides/requests.mdx +3 -1
- The client waits 30 seconds.
+ The client waits 60 seconds.
+ Override per request with timeout.
Nothing publishes until a human approves it.
From merge to draft PR, automatically.
This is what happens the moment a pull request merges on a connected repository. Run the simulation to watch one change go from merged code to a review-ready docs pull request.
No draft yet. Thally opens a pull request on your docs repository once the analysis finishes.
You decide what starts a draft.
Not every commit deserves a documentation review. Turn on the events that change your public surface; Thally ignores the rest.
Recent automation · jahce/dabs
A running log of what Thally drafted.
Every automated draft is traceable to the merge that caused it. Approve, edit, or dismiss; the loop keeps running.
docs: default timeout is now 60s
from jahce/bono #482 · 2 pages · high confidence
docs: document TimeoutError
from jahce/bono #482 · approved by jahce
docs: new --json flag on export
from jahce/leaflet #77 · approved by ada
docs: internal refactor note
from jahce/homesend #310 · no public surface change
Without automation
- Someone has to remember a merge affected the docs; usually nobody does.
- Drift is discovered by a confused customer or a failing example.
- Catching up means a big, dreaded documentation audit.
- Machine surfaces and AI context fall furthest behind.
Docs drift,
quietly.
With Automation
- Every relevant merge opens a reviewable draft within minutes.
- Each draft carries the diff and evidence behind it.
- Reviews are small and frequent, never a quarterly cleanup.
- Every surface regenerates together: humans and agents stay in sync.
Drafts arrive
on merge.
Works with the stack you already ship
Ship without wondering what the docs forgot.
Install the read-only GitHub App, choose your triggers, and every merge drafts its own documentation: reviewed by you, shipped on your say-so.