In a Terraform Cloud workspace linked to a version control repository, speculative plan runs start automatically when you merge or commit changes to version control.
In a Terraform Cloud workspace linked to a version control repository, speculative plan runs start automatically when you merge or commit changes to version control.
In a Terraform Cloud workspace linked to a version control repository, speculative plan runs start automatically when a pull request is made, not when you merge or commit changes. Merging or committing changes might trigger a regular plan run, but speculative plans are specifically tied to the review process of pull requests.
pull requests start speculative plans, this occurs before a commit or merge. https://developer.hashicorp.com/terraform/cloud-docs/run/remote-operations#speculative-plans
https://developer.hashicorp.com/terraform/cloud-docs/run/ui#automatically-starting-runs
It is true because Terraform Cloud can monitor the linked version control repository for changes and automatically trigger a speculative plan run in response to each commit or merge. This allows users to quickly see the expected changes that would result from the proposed change, without actually applying those changes. Speculative plan runs can be a useful tool for catching errors early in the development process and avoiding potentially costly mistakes.
Whether to perform speculative plans on pull requests to the connected repository, to assist in reviewing proposed changes. Automatic speculative plans are enabled by default, but you can disable them for any workspace. https://developer.hashicorp.com/terraform/cloud-docs/workspaces/settings/vcs