Emphasizing components over CI template contributions
What does this MR do and why?
Per #433240 (closed) This is the first MR that updates our contribution guide.
Over the past several years GitLab had accepted contributions from Partners and customers through CI templates, there were many challenges in this process, as explained in this issue https://gitlab.com/gitlab-org/gitlab/-/issues/433441+ In this MR we discourage users from continuing to contribute CI template and instead use the CI/CD catalog and component. In the upcoming MRs we are going to continue updating our contribution guide, to streamline community contribution of CI components with our community and partners
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.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.