pull_request_template.md

Description

A brief description of the changes introduced by this Pull Request.

PR title must follow Conventional Commits: <type>(optional scope): <description> (for example feat(vpc): add flow log support). This repository squash-merges, so the PR title becomes the commit subject that drives release notes and the SemVer bump. Append ! after the type/scope for a breaking change (for example feat(api)!: ...).

Issue or Ticket

Fixes #000

Type of change

• feat — a new user-facing feature (SemVer MINOR)
• fix — a bug fix (SemVer PATCH)
• docs — documentation only
• style — formatting/whitespace; no logic change
• refactor — code change that neither fixes a bug nor adds a feature
• perf — performance improvement
• test — adding or correcting tests
• build — build system or dependency changes
• ci — CI configuration (GitHub Actions, etc.)
• chore — maintenance task that does not fit elsewhere
• revert — reverts a previous commit

Breaking Changes

• Yes — this is a breaking change
• No

Breaking Changes Description

TODOs

• PR title follows Conventional Commits (<type>(scope): description).
• Validate your code matches the style of the project (tofu fmt -recursive).
• Update the docs (regenerate the terraform-docs block where applicable).
• Validate all tests run successfully, including pre-commit checks.
• Include release notes and description. This should include both a summary of the changes and any necessary context.