GitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsGitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsThis page is related to about.gitlab.com
and the GitLab handbook.
Merge requests are an important process where we peer review incoming changes to ensure code and content meets our standards and does not break any existing functionality.
In our continuous integration environment, people with merge permissions are the final check before content is released. Please use this privilege responsibly and ensure that merge requests align with our GitLab values.
We use javascript extensively throughout the website. Before updating a library, please ensure it doesn't break key locations as outlined in the rest of the regression test section. Additionally, please check the following javascript-related areas:
When reviewing and approving an MR in GitLab, there are some things to be aware of.
/includes/install/index.html
./install/
instead of the example above.https://patch-198261122213268859646.about.gitlab-review.app/install/
Sometimes a MR will be marked as "depends on" another merge request. This MR cannot be merged until the dependency is merged first. Documentation about merge request dependencies.