<!-- This issue requests a technical writer review as required for documentation content that was merged without one. --> <!-- NOTE: Please add a DevOps stage label (format `devops:<stage_name>`) and assign the technical writer who is [listed for that stage](https://about.gitlab.com/handbook/product/categories/#devops-stages). --> ## References Merged MR that introduced documentation requiring review: https://gitlab.com/gitlab-org/gitlab/merge_requests/18757 Related issue(s): https://gitlab.com/gitlab-org/gitlab/issues/29654 ## Further Details Good examples of workflow:rules and job:rules configuration are written up in `spec/services/ci/create_pipeline_service/rules_spec.rb` There is an open issue about using `workflow:rules` to control branch/tag/merge_request Pipelines, which is a major desired functionality: https://gitlab.com/gitlab-org/gitlab/issues/31685 This feature is currently feature-flagged (default to off) and will probably be turned on for Gitlab.com before we roll it out in a release to self-hosted customers.