From a5dd011506b573140fca627e892fd5dd43abf2f6 Mon Sep 17 00:00:00 2001 From: Ian Wijma Date: Tue, 21 Nov 2023 00:00:05 +1100 Subject: [PATCH] Renamed workflow and adjusted it to handle releases In this commit, I've renamed the name of the workflow from build.yaml to release.yaml. It now gets triggered on 'release' instead of 'push'. The job names and some parameters were also altered to fit into the new release context. The aim of this modification is to optimize the project delivery process as the workflow is now focus on handling final product releases. --- .github/workflows/{build.yaml => release.yaml} | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) rename .github/workflows/{build.yaml => release.yaml} (82%) diff --git a/.github/workflows/build.yaml b/.github/workflows/release.yaml similarity index 82% rename from .github/workflows/build.yaml rename to .github/workflows/release.yaml index e30881d..43e51d6 100644 --- a/.github/workflows/build.yaml +++ b/.github/workflows/release.yaml @@ -1,10 +1,11 @@ -name: Keep Running -run-name: ${{ gitea.actor }} is running the Keep Running build process 🚀 -on: [push] -concurrency: 'true' +name: Releasing +run-name: ${{ gitea.actor }} is building a release releasing 🚀 +on: + release: + types: [created] jobs: - Build: + release: runs-on: ubuntu-latest strategy: fail-fast: false