Documentation | GitLab Workflow updates (!173)

[Gedare Bloom (@gedare)]

Gedare Bloom commented on a discussion on user/support/contrib.md: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/173#note_123121

 > -like to create a fresh branch from `main` and then use `git-cherry-pick` to
 > -pull commits from your merge request branch on to the head of `main`. If you
 > -are having too much trouble, ask for help.
 > -
 > -## Approvers
 > -
 > -Merge Request approvals must be from a code owner, identified
 > -by the `CODEOWNERS` file and by sub-groups beneath `Approvers`.
 > -Any one who has requested approval permission can approve a merge request.
 > -Once a patch series is approved for integration into the RTEMS code base it can
 > -be merged by anyone with merge rights, which may include an automated bot.
 > -
 > -Approvers are volunteering their time so be polite. If you do not get a
 > -response to a merge request after five working days, please send a reminder
 > -on the merge request or send email to the {r:list}`devel`.
 > +```{include} ../../common/content/merge-request-creation.rst

I got it... .rst

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/173#note_123121
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250604/4e67a89b/attachment.htm>