diff --git a/docs/info/customizations.md b/docs/info/customizations.md
index c83a49403685571585c1cb3c55660698352fbe63..2f61de7e448f537e04a9e459a838a2789ad2aa5e 100644
--- a/docs/info/customizations.md
+++ b/docs/info/customizations.md
@@ -29,7 +29,7 @@ composer (previous major):
     PHP_VERSION: 8.1
 ```
 
-Variables can be defined in the project's `.gitlab-ci.yml` as above, or in the pipeline UI form when setting scheduled pipelines or running a pipeline manually. Form fields will override the values defined in the file or derived in the gitlab templates processing. This [variable precedence hierarchy](https://docs.gitlab.com/ee/ci/variables/index.html#cicd-variable-precedence) page has the full details. 
+Variables can be defined in the project's `.gitlab-ci.yml` as above, or in the pipeline UI form when setting scheduled pipelines or running a pipeline manually. Form fields will override the values defined in the file or derived in the gitlab templates processing. This [variable precedence hierarchy](https://docs.gitlab.com/ee/ci/variables/index.html#cicd-variable-precedence) page has the full details.
 
 ## Jobs
 
@@ -107,3 +107,16 @@ The name of the project being tested is derived from the `*.info.yml` file in th
 variables:
   PROJECT_NAME: 'my_project'
 ```
+
+## Workflow
+
+The [workflow](https://docs.gitlab.com/ee/ci/yaml/workflow.html) of a repository defines when pipelines will be run. Various events, such as creating a Merge Request, committing to the default branch or submitting via the pipeline UI can be used in combinations of rules, and if any of the conditions are true then the pipeline will be run. Gitlab Templates defines a [default workflow](https://git.drupalcode.org/project/gitlab_templates/-/blob/main/includes/include.drupalci.workflows.yml) which in most cases will be exactly what your project needs. However, if you do need to extend this default workflow, you can use the following:
+
+```
+workflow:
+  rules:
+    - !reference [ .default-workflow ]
+    - {add your extra rule here}
+    - {and another}
+```
+Using this syntax avoids duplicating the entire default workflow, and ensures your project will get any updates or improvements made to the standard workflow.
diff --git a/includes/include.drupalci.workflows.yml b/includes/include.drupalci.workflows.yml
index f19206a4a4fc28912397164e58d171b2eca04563..3c9b34011e40fb72f3f9f63135a5d9659cab703b 100644
--- a/includes/include.drupalci.workflows.yml
+++ b/includes/include.drupalci.workflows.yml
@@ -13,22 +13,27 @@
 # https://gitlab.com/help/ci/pipelines/schedules
 ################
 
+# Define the default workflow rule as a re-usable reference so that these can be extended
+# with additional rules if a customized workflow is required.
+.default-workflow: &default-workflow
+  # These 3 rules from https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Workflows/MergeRequest-Pipelines.gitlab-ci.yml
+  # Run on merge requests
+  - if: $CI_MERGE_REQUEST_IID
+  - if: $CI_PIPELINE_SOURCE == 'merge_request_event'
+  # Run on tags
+  - if: $CI_COMMIT_TAG
+  # Run when called from an upstream pipeline https://docs.gitlab.com/ee/ci/pipelines/downstream_pipelines.html?tab=Multi-project+pipeline#use-rules-to-control-downstream-pipeline-jobs
+  - if: $CI_PIPELINE_SOURCE == 'pipeline'
+  - if: $CI_PIPELINE_SOURCE == 'parent_pipeline'
+  # Run on commits to the default & release branches.
+  - if: ($CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH || $CI_COMMIT_BRANCH =~ /^[78]\.x-\d+\.x$|^[\d+.]+\.x$/) && $CI_PROJECT_ROOT_NAMESPACE == "project"
+  # The last rule above blocks manual and scheduled pipelines on non-default branch. The rule below allows them:
+  - if: $CI_PIPELINE_SOURCE == "schedule"
+  # Run if triggered from Web using 'Run Pipelines'
+  - if: $CI_PIPELINE_SOURCE == "web"
+  # Run if triggered from WebIDE
+  - if: $CI_PIPELINE_SOURCE == "webide"
+
 workflow:
   rules:
-    # These 3 rules from https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Workflows/MergeRequest-Pipelines.gitlab-ci.yml
-    # Run on merge requests
-    - if: $CI_MERGE_REQUEST_IID
-    - if: $CI_PIPELINE_SOURCE == 'merge_request_event'
-    # Run on tags
-    - if: $CI_COMMIT_TAG
-    # Run when called from an upstream pipeline https://docs.gitlab.com/ee/ci/pipelines/downstream_pipelines.html?tab=Multi-project+pipeline#use-rules-to-control-downstream-pipeline-jobs
-    - if: $CI_PIPELINE_SOURCE == 'pipeline'
-    - if: $CI_PIPELINE_SOURCE == 'parent_pipeline'
-    # Run on commits to the default & release branches.
-    - if: ($CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH || $CI_COMMIT_BRANCH =~ /^[78]\.x-\d+\.x$|^[\d+.]+\.x$/) && $CI_PROJECT_ROOT_NAMESPACE == "project"
-    # The last rule above blocks manual and scheduled pipelines on non-default branch. The rule below allows them:
-    - if: $CI_PIPELINE_SOURCE == "schedule"
-    # Run if triggered from Web using 'Run Pipelines'
-    - if: $CI_PIPELINE_SOURCE == "web"
-    # Run if triggered from WebIDE
-    - if: $CI_PIPELINE_SOURCE == "webide"
+    - *default-workflow