The statement incorrectly identifies the trigger for speculative plan runs. In an HCP Terraform or Terraform Cloud workspace linked to a version control system (VCS), speculative plans are automatically initiated when a pull request (or merge request) is opened. They are designed to show the potential outcome of merging the proposed changes. In contrast, committing or merging changes directly to the main tracked branch of the repository triggers a standard plan and potentially an apply, not a speculative plan.

The statement is false because it confuses the trigger for a speculative plan with the trigger for a standard run. A speculative plan is for a proposed change (a pull request), allowing for review before merging. A standard run is for an actual change committed to the tracked branch.

1. HashiCorp Terraform Documentation, "VCS-Driven Runs": In the section "Speculative Plans on Pull Requests," the documentation explicitly states: "When you create a pull request (or merge request) in your connected VCS repository, Terraform Cloud automatically starts a speculative plan in the associated workspace. This helps you verify whether the change will have the intended effect before merging it." This directly contradicts the question's claim that merges or commits trigger speculative plans.

2. HashiCorp Terraform Documentation, "Run Modes and Options": Under the "Speculative Plans" section, the documentation clarifies their purpose: "Speculative plans are plans that Terraform Cloud runs on proposed changes, such as pull requests or merge requests. They let you see the potential effects of a change before you decide whether to merge and apply it." This reinforces that the trigger is a proposed change, not a finalized merge or commit.

3. HashiCorp Terraform Documentation, "VCS-Driven Runs": The section "Standard Runs on Merges" describes the correct behavior for merges: "When you merge a pull request, Terraform Cloud automatically starts a new run in the associated workspace. Depending on the workspace's settings, this can be an apply run or a plan-only run." This clearly distinguishes the standard run triggered by a merge from the speculative plan triggered by opening a pull request.