Repository navigation
docs(self-driving): document agent handoff, PR state, and stacked PRs - #20869
andrewm4894 merged 3 commits into
Conversation
Generated-By: PostHog Desktop Task-Id: da0d619e-10f7-4c82-a7b0-26cfd5bbf694
Deploy preview
Changed pages
|
|
Vale prose linter → found 0 errors, 2 warnings, 0 suggestions in your markdown Full report → Copy the linter results into an LLM to batch-fix issues. Linter being weird? Update the rules! |
|
PostHog Review alpha 🦔 If you find any issues helpful - please reply "valid", "invalid", etc., for evaluation purposes 🙏 |
|
|
||
| ## Stacked pull requests | ||
|
|
||
| Research can split a large change into dependent layers. PostHog creates a child report and pull request for each layer. A layer starts after its dependency has a pull request. Its pull request uses the dependency branch as its base until that dependency merges, so you can review and merge the layers in order. |
There was a problem hiding this comment.
Document the base change required between stacked merges
Should fix · documentation
The phrase 'until that dependency merges' implies that merging the dependency changes the child PR's base. dependency_head_branch selects the base when implementation starts; the merge handler does not change it later. GitHub automatically changes dependent PR bases when the merged branch is deleted. If that branch remains, merging the next layer updates the dependency branch instead of the intended target branch.
Suggested fix
Describe base selection when the layer starts. Add a step after each dependency merges: verify the next PR's base and change it to the intended target branch if necessary. Explain that deleting the merged dependency branch triggers GitHub's automatic base change.
The copied prompt links to the report and tells the agent to read and claim it through PostHog MCP tools. State that the agent must be able to use the PostHog MCP server, and link to its setup docs. Generated-By: PostHog Desktop Task-Id: 3ae19e68-05c6-4265-8400-140d1c861e07
…d PRs PostHog sets a layer's pull request base once, when the layer starts, and does not change it after the dependency merges. Describe how the base is chosen, and tell readers to delete the merged branch (so GitHub retargets the next pull request) or change the base themselves. Generated-By: PostHog Desktop Task-Id: 3ae19e68-05c6-4265-8400-140d1c861e07
Bundle reportTotal JS (gzip)9.78 MiB (+0.0 KiB / +0.0%) Eager graph (modules shipped in each entrypoint's initial chunks)
Largest modules in the
|
| Module | Size |
|---|---|
./src/data/mcp-tools.json |
1318.5 KiB |
css ./node_modules/.pnpm/css-loader@5.2.7_webpack@5.101.3/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[1]!./node_modules/.pnpm/postcss-loader@4.3.0_postcss@8.5.6_webpack@5.101.3/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[2]!./src/styles/global.css |
804.9 KiB |
./src/components/Stickers/Stickers.tsx |
696.4 KiB |
./node_modules/.pnpm/@radix-ui+react-icons@1.3.2_react@18.3.1/node_modules/@radix-ui/react-icons/dist/react-icons.esm.js |
481.4 KiB |
./node_modules/.pnpm/@posthog+brand@0.8.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/x-ray.mjs |
480.8 KiB |
./node_modules/.pnpm/@posthog+brand@0.8.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/trenchcoat.mjs |
447.5 KiB |
./node_modules/.pnpm/rehype-raw@7.0.0/node_modules/rehype-raw/lib/index.js + 29 modules |
395.1 KiB |
./node_modules/.pnpm/@posthog+brand@0.8.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/im-the-driver.mjs |
385.7 KiB |
./src/hooks/useCustomers.tsx + 56 modules |
375.9 KiB |
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js |
354.8 KiB |
./node_modules/.pnpm/react-markdown@8.0.7_@types+react@16.14.66_react@18.3.1/node_modules/react-markdown/lib/react-markdown.js + 88 modules |
351.4 KiB |
./src/components/ProductComparisonTable/index.tsx + 127 modules |
310.3 KiB |
./node_modules/.pnpm/cloudinary-core@2.14.0_lodash@4.17.21/node_modules/cloudinary-core/cloudinary-core.js |
281.9 KiB |
./node_modules/.pnpm/@posthog+brand@0.8.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/doll-house.mjs |
281.7 KiB |
./node_modules/.pnpm/@posthog+brand@0.8.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/director.mjs |
275.6 KiB |
Eager-graph budgets are report-only until a baseline is established. Sizes are gzip of public/**/*.js; eager size is webpack module source bytes for the modules actually shipped in the entrypoint's initial chunks (post-tree-shake).

Changes
This PR adds three sections to the self-driving implementation guide. The guide describes only the hosted implementation path. Readers do not find the other handoff and review options that the product supports.
Source of truth:
products/signals/frontend/inbox/components/detail/implementationAgents.tsxin PostHog/posthog (PostHog/posthog#112270).This is a content PR with no visual or navigation change. Open PRs #18512 and #19136 also edit this page. This PR adds new sections only, so the merge conflict risk is low.
Checks:
pnpm formatorpnpm start.Checklist
vercel.json(no page moved)Created with PostHog Desktop from this inbox report.
🤖 Generated with Claude Code
Origin