- Pipeline information
- Post-merge pipeline status
- Merge when pipeline succeeds (MWPS)
- Live preview with Review Apps
- License compliance
- External status checks
The Overview page of a merge request displays status updates from services that perform actions on your merge request. All subscription levels display a widgets area, but the content of the area depends on your subscription level and the services you configure for your project.
- Both pre-merge and post-merge pipelines, and the environment information, if any.
- Which deployments are in progress.
When a merge request is merged, you can see the post-merge pipeline status of the branch the merge request was merged into. For example, when a merge request is merged into the default branch and then triggers a deployment to the staging environment.
Ongoing deployments are shown, and the state (deploying or deployed)
for environments. If it’s the first time the branch is deployed, the link
404 error until done. During the deployment, the stop button is
disabled. If the pipeline fails to deploy, the deployment information is hidden.
For more information, read about pipelines.
Set a merge request that looks ready to merge to merge automatically when CI pipeline succeeds.
If you configured Review Apps for your project, you can preview the changes submitted to a feature branch through a merge request on a per-branch basis. You don’t need to check out the branch, install, and preview locally. All your changes are available to preview by anyone with the Review Apps link.
With GitLab Route Maps set, the merge request widget takes you directly to the pages changed, making it easier and faster to preview proposed modifications.
If you have configured License Compliance for your project, then you can view a list of licenses that are detected for your project’s dependencies.