Repository navigation
Adopt recipient message example guidance for Help reviews - #409
Conversation
✅ Deploy Preview for legendary-lollipop-e2d131 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
@codex review Please review exact head |
|
Codex Review: Didn't find any major issues. Keep it up! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Adoption verifiedHelp main now pins editorial Main Build 38167653958 passed on the exact merge revision. Normal Netlify production deploy The four canonical guidance files returned HTTP 200 with the expected committed bytes. The existing assignment articles in both languages and all 24 selected PNGs also returned HTTP 200 with unchanged approved hashes. This update changes the review guidance and its pinned consumer version; it does not claim that recipient examples have already been added to existing articles. Canonical recipient guidance: https://github.com/hellotext/editorial/blob/d0ee357e45d2d14ae605081fc8fe20763b1bb4ba/messages.md#recipient-examples-in-help-articles |
Summary
Adopt the merged shared editorial guidance from hellotext/editorial#14 through the pinned
docs/editorialsubmodule.Every applicable Help review must consider an early recipient message example using the existing message component and an actual supported channel. Useful examples go after the introduction and before configuration instructions, in the article language. An unhelpful example requires a concrete omission reason; useful examples that cannot yet be prepared remain pending.
The rule remains in the canonical shared guide, message guidance and workflow. This consumer change only updates the submodule pin.
Verification
docs/andAGENTS.mdremain absent from both language builds.