Cloud Build triggers a build on every commit to master; you need an automated way to release specific commits. What should you do?

Creating a build trigger on a Git tag pattern is the most effective and automated way to release specific commits. Git tags are designed to mark specific points in history as important, such as release versions. By configuring Cloud Build to trigger only when a tag matching a release pattern (e.g., v..) is pushed, you ensure that builds for releases are automated and tied directly to your versioning strategy. Manually triggering builds is not automated and can lead to human error. Creating a trigger on a Git branch name pattern is less precise for releases, as branches are typically for ongoing development and merge into master, rather than marking specific release points. Using a second repository adds unnecessary complexity and overhead for managing releases.