Release post content for workflow: rules:

data/features.yml

@@ -6543,6 +6543,23 @@ features:
     gitlab_com: true
     github_com: false
     github_enterprise: false
+  - title: "Set rules for triggering pipeline in entirety"
+    description: |
+      Define rules to decide whether an entire pipeline is run, using `workflow: rules:` 
+      keyword provides a global setting that is evaluated first when determining if a
+      pipeline should run.
+    link_description: "Documentation"
+    link: "https://docs.gitlab.com/ee/ci/yaml/README.html#workflowrules"
+    solution: Verify
+    category:
+      - continuous_integration
+    gitlab_core: true
+    gitlab_starter: true
+    gitlab_premium: true
+    gitlab_ultimate: true
+    gitlab_com: true
+    github_com: false
+    github_enterprise: false  
   - title: "Windows Container Executor"
     description: |
         With this feature you are able to use Docker containers on Windows directly,

data/release_posts/unreleased/ci-pipeline_trigger.yml

+features:
+  secondary:
+    - name: "Set rules for triggering an entire pipeline"
+      available_in: [core, starter, premium, ultimate]
+      documentation_link: 'https://docs.gitlab.com/ee/ci/yaml/README.html#workflowrules'
+      reporter: thaoyeager
+      stage: verify
+      issue_url: 'https://gitlab.com/gitlab-org/gitlab/issues/29654'
+      description: |
+        Sometimes you want to define rules to decide whether an entire pipeline is run. For example, you may want a pipeline to only run on the master branch. The only way to do that before this release was to add the rule to each job. So you would end up adding duplicate criteria to every single job in the pipeline, and then if none of them end up resolving to true, the entire pipeline is skipped. This new `workflow: rules:` keyword provides more efficiency by allowing a global setting for a pipeline that is evaluated first when determining if a pipeline should run.