Make Inki review verify docs against the strapi PR they document#3305
Merged
Conversation
…t it When a strapi/documentation PR description references a strapi/strapi or strapi/cloud code PR, /inki:review now detects it and verifies the docs against that PR's head instead of develop or a possibly-stale local clone. This prevents false 'config key/value does not exist' findings when the documented code change is still unmerged, and lets the coherence checker tell a real contradiction apart from a sibling page that simply has not been updated yet.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pwizla
commented
Jun 30, 2026
pwizla
left a comment
Collaborator
Author
There was a problem hiding this comment.
LGTM, let's go! Should fix some review errors I noticed today
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.
This PR makes /inki:review detect when a strapi/documentation PR description references a strapi/strapi or strapi/cloud code PR (e.g. strapi/strapi#26737) and verify the documentation against that code PR's head instead of develop or a possibly-stale local clone. The target resolver now reads the PR body and exposes the referenced code PRs, the code-verifier treats the referenced PR as its primary source of truth so an unmerged change is no longer flagged as a nonexistent config key or value, and the coherence checker uses it to tell a real contradiction apart from a sibling page that has not been updated yet.