BAU: Remove branch specifier from terraform-ci

[whi-tw]

What problem does this pull request solve?

We sometimes create PRs against feature branches when working on
multi-PR changes. The branch specifier meant that the terraform-ci
workflow would not run for these PRs which was unhelpful.

Things to consider when reviewing

• Ensure that you consider the wider context.
• Does it work when run on your machine?
• Is it clear what the code is doing?
• Do the commit messages explain why the changes were made?
• Are there all the unit tests needed?
• Has all relevant documentation been updated?

Reminders

If you've made changes to the deployer role (files in modules/deployer-access):

• Remember to run make <environment> forms/account apply on the relevant environments (dev, staging, user-research, and/or prod)
• Check the #govuk-forms-deployment-notifications Slack channel to ensure the apply-forms-terraform-<environment> pipelines have run successfully

[Copilot]

Pull Request Overview

This PR removes the branch specifier from the terraform-ci workflow to enable it to run on pull requests targeting any branch, not just main. This allows the workflow to execute when creating PRs against feature branches during multi-PR development work.

• Removed branches: [main] constraint from the pull_request trigger in terraform-ci workflow

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sarahseewhy]

I can see why this change is required 🚀

I'd be curious to know why we originally limited the PR to just main. Git history isn't helpful unfortunately.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.