Advance Docs Agent publication base fix - #120
Merged
Merged
Conversation
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.
Summary
53f43bc6v0.12.27Why
The previous acceptance run reached publication but Docs Agent omitted the explicit
trunkpublication base, causing WP Codebox to fall back tomain: https://github.com/Automattic/build-with-wordpress/actions/runs/29645661510Docs Agent Automattic/docs-agent#159 now forwards
base_refto both workspace materialization and publication.How to test
pnpm install --frozen-lockfile.53f43bc6433d2631750edabcb458a77db55aa8cband WP Codeboxv0.12.27at its immutable release commit.DOCS_AGENT_DIR=/path/to/docs-agent WP_CODEBOX_DIR=/path/to/wp-codebox pnpm test.pnpm build && pnpm verify.Compatibility
trunkbase instead of an implicitmainfallback.AI assistance