Document updating the consent string to unlock private APIs. - #55235
Conversation
|
Warning: Type of PR label error To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.
Read more about Type labels in Gutenberg. |
Co-authored-by: Andrew Serong <14988353+andrewserong@users.noreply.github.com>
|
Flaky tests detected in 53552fe. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/6488677634
|
There was a problem hiding this comment.
Looks great to me and I think this is the right place for this note. It's for Gutenberg maintainers working with the private-apis package and not for folks just looking for usage examples in handbook. Thank you!
Perhaps this could also be documented in the release checklist at https://make.wordpress.org/core/handbook/about/release-cycle/block-editor-release-process-for-major-releases/?
I'll add something to the private APIs section of the page. Am I correct in thinking the page is managed directly in the handbook rather than via a markdown to HTML converter? |
Yes |
What?
Documenting the process for updating the consent string to unlock access to private APIs.
Why?
The consent string is intended to be updated on a regular basis.
How?
I've put it in the package's readme file for now, please advise if it should be moved elsewhere.
Testing Instructions
N/A: Docs change.
Testing Instructions for Keyboard
N/A: Docs change.
Screenshots or screencast
N/A: Docs change.