Add latest changes from gitlab-org/gitlab@master

2 files changed, 10 insertions, 0 deletions

diff --git a/doc/ci/pipelines/downstream_pipelines.md b/doc/ci/pipelines/downstream_pipelines.md
index ffcfee98f05..9de1e225a81 100644
--- a/doc/ci/pipelines/downstream_pipelines.md
+++ b/doc/ci/pipelines/downstream_pipelines.md
@@ -661,6 +661,12 @@ For example, in a [multi-project pipeline](#multi-project-pipelines):
          artifacts: true
    ```
 
+### Control what type of variables to forward to downstream pipelines
+
+Use the [`trigger:forward` keyword](../yaml/index.md#triggerforward) to specify
+what type of variables to forward to the downstream pipeline. Forwarded variables
+are considered trigger variables, which have the [highest precedence](../variables/index.md#cicd-variable-precedence).
+
 ## Troubleshooting
 
 ### Trigger job fails and does not create multi-project pipeline
diff --git a/doc/ci/variables/index.md b/doc/ci/variables/index.md
index 64a0f1038ad..1e50756d08f 100644
--- a/doc/ci/variables/index.md
+++ b/doc/ci/variables/index.md
@@ -718,6 +718,10 @@ use this setting for control over the environment the pipeline runs in.
   The example can be copied to your own group or instance for testing. More details
   on what other GitLab CI patterns are demonstrated are available at the project page.
 
+- You can [pass CI/CD variables to downstream pipelines](../pipelines/downstream_pipelines.md#pass-cicd-variables-to-a-downstream-pipeline).
+  Use [`trigger:forward` keyword](../yaml/index.md#triggerforward) to specify what type of variables
+  to pass to the downstream pipeline.
+
 ## Troubleshooting
 
 ### List all variables