Merge Request for onboarding

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.

MR for onboarding for xuid0

Open a merge request Go to the community fork on GitLab.com.

If you don’t see this message, on the left sidebar, select Code > Merge requests > New merge request.

Take a look at the branch names. You should be merging from your branch in the community fork to the master branch in the GitLab repository.

Fill out the information and then select Save changes. Don’t worry if your merge request is not complete.

If you don’t want anyone from GitLab to review it, you can select the Mark as draft checkbox. If you’re not happy with the merge request after you create it, you can close it, no harm done.

If you’re happy with this merge request and want to start the review process, type @gitlab-bot ready in a comment and then select Comment.

Someone from GitLab will look at your request and let you know what the next steps are. For details, see the merge request workflow.

Have questions? Use @gitlab-bot help to ping a GitLab Merge Request coach. For more information on MR coaches, visit How GitLab

https://docs.gitlab.com/ee/development/contributing/#open-a-merge-request

References

https://gitlab.com/gitlab-community/gitlab https://docs.gitlab.com/ee/development/contributing/#choose-a-development-environment

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.