GitLab CI/CD包含工作流时变量被完全覆盖而非追加问题

GitLab CI里直接重新定义workflow会完全覆盖include进来的配置，要实现只修改指定变量、保留原有变量，有两种靠谱的实现方式：

方法一：用YAML锚点+合并键复用基础配置 #

在仓库1的test-ci.yml中，把基础workflow配置定义为锚点，方便仓库2复用并合并变量：

# 仓库1 test-ci.yml
.workflow-base: &workflow-base
  rules:
    - if: '$CI_COMMIT_BRANCH == "main"'
      variables:
        SOME_VARIABLE: "main-value"
        SECOND_VARIABLE: "main-second"
    - if: '$CI_COMMIT_BRANCH == "non-prod"'
      variables:
        SOME_VARIABLE: "non-prod-value"
        SECOND_VARIABLE: "non-prod-second"

# 导出锚点供其他仓库引用
workflow: *workflow-base

仓库2的.gitlab-ci.yml中，通过锚点合并原有配置，仅修改目标变量：

# 仓库2 .gitlab-ci.yml
include:
  - project: 'path/to/仓库1'
    file: 'test-ci.yml'

# 复用基础workflow规则，仅覆盖指定变量
workflow:
  <<: *workflow-base
  rules:
    - if: '$CI_COMMIT_BRANCH == "main"'
      variables:
        SECOND_VARIABLE: "custom-main-second"  # 只替换这个变量
    - if: '$CI_COMMIT_BRANCH == "non-prod"'
      variables:
        SECOND_VARIABLE: "custom-non-prod-second"  # 只替换这个变量

方法二：用extends关键字继承模板 #

若觉得锚点语法不够直观，可使用extends定义可继承的workflow模板：

# 仓库1 test-ci.yml
.workflow-template:
  rules:
    - if: '$CI_COMMIT_BRANCH == "main"'
      variables:
        SOME_VARIABLE: "main-value"
        SECOND_VARIABLE: "main-second"
    - if: '$CI_COMMIT_BRANCH == "non-prod"'
      variables:
        SOME_VARIABLE: "non-prod-value"
        SECOND_VARIABLE: "non-prod-second"

workflow:
  extends: .workflow-template

仓库2继承模板后，重写指定分支的变量配置：

# 仓库2 .gitlab-ci.yml
include:
  - project: 'path/to/仓库1'
    file: 'test-ci.yml'

workflow:
  extends: .workflow-template
  rules:
    - if: '$CI_COMMIT_BRANCH == "main"'
      variables:
        SECOND_VARIABLE: "custom-main-second"  # 仅覆盖该变量
    - if: '$CI_COMMIT_BRANCH == "non-prod"'
      variables:
        SECOND_VARIABLE: "custom-non-prod-second"  # 仅覆盖该变量

原理说明 #

GitLab CI的配置规则是：当重新定义整个workflow块时，会直接替换include进来的同名块，而非合并内部变量。上述两种方法都是通过复用原有规则结构，仅修改需要替换的变量条目，从而保留SOME_VARIABLE这类无需改动的变量。

内容的提问来源于stack exchange，提问作者benrieger