RP item template: Add tip about using the MR Review App
To suggest a change to the Product Handbook, please review the updating the Product Handbook section.
This isn't exactly a handbook update, but relates to processes, so I figured it was worth using the template.
Related to:
Please provide a brief explanation for this change:
As part of the release post 14.9 retrospective, I noted challenges with previewing content blocks before assembly. It turns out this is already possible and quite easy with the existing Review App! Thus, adding a tip to the RP item MR template seemed appropriate so that we can catch errors earlier in the RP process. See #13133 (comment 896800255)
You can verify that Review Apps are set up on RP MRs by selecting "View app" on this MR that is currently active: !101638 (merged)
Please indicate the types of revisions being suggested for the Product Handbook (please check all that apply):
-
Small improvement (typos, clarifications, etc.) -
Adding a new section -
Modifying existing section -
Documenting a new process -
Adding a new page or directory -
Other
Please indicate Milestone
-
Assigned to Milestone
Author Checklist
-
Provided a concise title for the MR -
Provided a brief explanation for this change (Say why, not just what) - (Attach screenshots, Slack conversations, etc. as necessary)
-
Indicated the types of changes included in this MR -
Verified that no confidential data is in this MR -
Assigned reviewers for this change to the correct DRI(s) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
- If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
- [-] If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #product or #whats-happening-at-gitlab linking to this MR.
- If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.