Set AST_ENABLE_MR_PIPELINES: false

What does this MR do?

As discussed AST_ENABLE_MR_PIPELINES is set for all secure p... (gitlab-org/gitlab#556262 - closed) • Adam Cohen • 18.3, any project that includes analyzer.yml or go.yml has now set AST_ENABLE_MR_PIPELINES: true, which causes these projects to switch from branch pipelines to merge request pipelines. This MR sets AST_ENABLE_MR_PIPELINES: false to disable this behaviour. Individual projects can override this behaviour by overriding AST_ENABLE_MR_PIPELINES at the job-level.

What are the relevant issue numbers?

AST_ENABLE_MR_PIPELINES is set for all secure p... (gitlab-org/gitlab#556262 - closed) • Adam Cohen • 18.3

Does this MR meet the acceptance criteria?

• Tests added for this feature/bug

  • Before this change

    When a project includes go.yml, two pipelines are created for a merge request:

    • Branch Pipeline
    • Merge Request Pipeline

  • After this change

    • When a project includes go.yml, only a single branch pipeline is created for a merge request:
      • Branch Pipeline
    • When a project includes go.yml, and explicitly sets AST_ENABLE_MR_PIPELINES: true, two pipelines are created for the merge request:
      • Branch Pipeline
      • Merge Request Pipeline