From 818490457bb79cfddc0e6bbcf0cae4f1e7d219ac Mon Sep 17 00:00:00 2001 From: TheGiddyLimit Date: Wed, 9 Nov 2022 15:32:35 +0000 Subject: [PATCH] feat(build): prefer releasing on tag to releasing on merge to master The former was set up in order to avoid having release branches, but produces more problems than it solves if multiple people are contributing to the repository. Instead, only build on tagged release versions, whatever branch they happen to be in. In order to ensure random PRs don't trigger releases, tag protection has now been added to the repo, allowing only admins/maintainers to push version tags. --- .github/workflows/{push-master.yaml => release.yaml} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename .github/workflows/{push-master.yaml => release.yaml} (95%) diff --git a/.github/workflows/push-master.yaml b/.github/workflows/release.yaml similarity index 95% rename from .github/workflows/push-master.yaml rename to .github/workflows/release.yaml index 89d3c5e..7baa33f 100644 --- a/.github/workflows/push-master.yaml +++ b/.github/workflows/release.yaml @@ -2,8 +2,8 @@ name: Build and Deploy on: push: - branches: - - master + tags: + - 'v[0-9]+.[0-9]+.[0-9]+' jobs: build-and-deploy: