summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2023-03-10 23:40:33 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2023-03-10 23:40:33 +0000
commitdb87b632cbadc272dee1acbb10d226680f7212a2 (patch)
tree57c6d27074b778e28f382f51ce7826dab3227bcf /scripts
parentd244360d8b38218bd3e71c0203e9f2af41498daa (diff)
downloadgitlab-ce-db87b632cbadc272dee1acbb10d226680f7212a2.tar.gz
Add latest changes from gitlab-org/gitlab@15-9-stable-ee
Diffstat (limited to 'scripts')
-rwxr-xr-xscripts/create-pipeline-failure-incident.rb2
1 files changed, 0 insertions, 2 deletions
diff --git a/scripts/create-pipeline-failure-incident.rb b/scripts/create-pipeline-failure-incident.rb
index 2b86fac680d..bd57abf3740 100755
--- a/scripts/create-pipeline-failure-incident.rb
+++ b/scripts/create-pipeline-failure-incident.rb
@@ -170,8 +170,6 @@ class CreatePipelineFailureIncident
Additionally, a message can be posted in `#backend_maintainers` or `#frontend_maintainers` to get a maintainer take a look at the fix ASAP.
- Cherry picking a change that was used to fix a similar master-broken issue.
- In both cases, make sure to add the ~"pipeline:expedite" label to speed up the `stable`-fixing pipelines.
-
### Resolution
Add a comment to this issue describing how this incident could have been prevented earlier in the Merge Request pipeline (rather than the merge commit pipeline).