Repository navigation
docs(blocks): a worked guide for running many locations from one set of prompts - #98
Closed
dhruva-vapi wants to merge 2 commits into
Closed
dhruva-vapi wants to merge 2 commits into
dhruva-vapi wants to merge 2 commits into
Conversation
This was referenced Nov 19, 2026
Contributor
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
dhruva-vapi
force-pushed
the
docs/many-locations-guide
branch
from
November 19, 2026 16:31
aa555eb to
e71506f
Compare
dhruva-vapi
marked this pull request as ready for review
November 20, 2026 18:24
…of prompts The blocks page is a reference. This adds the path through it for someone who runs the same agent at several locations: move pasted wording and settings into blocks, deploy, give one location its own wording or setting, change a shared block through a pull request, roll it out, and what promotion and pull do along the way. Every command in the guide was run in a scratch copy with the example's two clinics against a local stand-in for the API, and the page says so. It also states three things the reference pages leave implicit: promotion copies every file in the pipeline's patterns, a block used only outside those patterns stays on the sync-blocks list after a promotion, and pushing a file does not remove a setting that exists only in the dashboard. The blocks page said "to discard the dashboard edit, change nothing". That holds for a value the file sets. It now also says that a field the file does not set stays as the dashboard left it, and that naming the field in the file is how to clear it, marked as seen on the stand-in. README, the blocks, promotion and file-formats pages, the example's README and AGENTS.md link to the guide. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
devin-ai-integration
Bot
force-pushed
the
feat/blocks
branch
from
November 21, 2026 03:54
bd98584 to
c6635bd
Compare
devin-ai-integration
Bot
force-pushed
the
docs/many-locations-guide
branch
from
November 21, 2026 03:54
e71506f to
169357d
Compare
Contributor
|
Replaced by #112 (same commits rebased onto main, opened as the Devin bot so it can be approved). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Value
V.A.L.U.E. tier: micro. One guide and the links to it. No engine change.
What's in it
One new page,
docs/guides/many-locations.md, that follows the example's two clinics through the whole job:templates/blocks/and shared settings intotemplates/config/, with the one-line marker for each.resources/<org>/templates/) and its own setting (a key beside$include), and what "the file's own keys win" does across later block edits.pulldoes with a file that uses blocks.README, the blocks, promotion and file-formats pages, the example's README and AGENTS.md link to it. The reference pages keep their role, and the guide links to them instead of repeating them.
The guide also states three things the reference pages leave implicit. Each was seen in the run described below:
sync-blockslist.--resolve=oursdoes not remove a setting that exists only in the dashboard.Verification
tests/docs-links.test.ts1/1,tests/docs-commands.test.ts2/2,tests/examples.test.ts4/4,tests/agent-docs.test.ts4/4. The full suite was left to CI.Things to know
src/ortests/.@include,$include,templates/blocks/,templates/config/,sync-blocks) are written as the code has them today. If one changes, the guide changes with the reference page.nullin the file clears it, rests on the stub. The first matches the PATCH rule indocs/learnings/assistants.md. Neither has been tried on a live org, and both pages say so.Stack
Fourth of four. Sits on #94 (blocks), which sits on #96 and #97.