Merge branch 'update-danger-specs-message' into 'master'

Mention the 'pipeline:run-as-if-foss' label in danger/specs/Dangerfile

See merge request gitlab-org/gitlab!72217

danger/specs/Dangerfile

@@ -20,7 +20,7 @@ Please make sure the spec files pass in AS-IF-FOSS mode either:
 
 1. Locally with `FOSS_ONLY=1 bin/rspec -- %<spec_files>s`.
 1. In the MR pipeline by verifying that the `rspec foss-impact` job has passed.
-1. In the MR pipelines by including `RUN AS-IF-FOSS` in the MR title (you can do it with the ``/title %<mr_title>s [RUN AS-IF-FOSS]`` quick action) and start a new MR pipeline.
+1. In the MR pipelines by setting the ~"pipeline:run-as-if-foss" label on the MR (you can do it with the `/label ~"pipeline:run-as-if-foss"` quick action) and start a new MR pipeline.
 
 MSG
 
@@ -46,7 +46,7 @@ end
 
 # The only changes outside `ee/` are in `spec/`
 if has_ee_app_changes && has_spec_changes && !(has_app_changes || has_ee_spec_changes)
-  warn format(EE_CHANGE_WITH_FOSS_SPEC_CHANGE_MESSAGE, spec_files: spec_changes.join(" "), mr_title: gitlab.mr_json['title']), sticky: false
+  warn format(EE_CHANGE_WITH_FOSS_SPEC_CHANGE_MESSAGE, spec_files: spec_changes.join(" ")), sticky: false
 end
 
 # Forbidding a new file addition under `/spec/controllers` or `/ee/spec/controllers`

doc/development/ee_features.md

@@ -40,7 +40,7 @@ By default, merge request pipelines for development run in an EE-context only. I
 developing features that differ between FOSS and EE, you may wish to run pipelines in a
 FOSS context as well.
 
-To run pipelines in both contexts, include `RUN AS-IF-FOSS` in the merge request title.
+To run pipelines in both contexts, add the `~"pipeline:run-as-if-foss"` label to the merge request.
 
 See the [As-if-FOSS jobs](pipelines.md#as-if-foss-jobs) pipelines documentation for more information.