Commit 11bc890e authored by Daniel Gruesso's avatar Daniel Gruesso Committed by Marcin Sedlak-Jakubowski

Add note for red merge button to MR docs

parent 166453a4
...@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w ...@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
type: index, reference type: index, reference
--- ---
# Reviewing and managing merge requests # Reviewing and managing merge requests **(CORE)**
Merge requests are the primary method of making changes to files in a GitLab project. Merge requests are the primary method of making changes to files in a GitLab project.
Changes are proposed by [creating and submitting a merge request](creating_merge_requests.md), Changes are proposed by [creating and submitting a merge request](creating_merge_requests.md),
...@@ -203,6 +203,11 @@ If there's an [environment](../../../ci/environments/index.md) and the applicati ...@@ -203,6 +203,11 @@ If there's an [environment](../../../ci/environments/index.md) and the applicati
successfully deployed to it, the deployed environment and the link to the successfully deployed to it, the deployed environment and the link to the
Review App will be shown as well. Review App will be shown as well.
NOTE: **Note:**
When the default branch (for example, `main`) is red due to a failed CI pipeline, the `merge` button
When the pipeline fails in a merge request but it can be merged nonetheless,
the **Merge** button will be colored in red.
### Post-merge pipeline status ### Post-merge pipeline status
When a merge request is merged, you can see the post-merge pipeline status of When a merge request is merged, you can see the post-merge pipeline status of
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment