Split release creation from actual package build #28
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nanory
force-pushed
the
feature/25-split-release-creation
branch
2 times, most recently
from
369ee95 to
c87419c
Compare
nanory
force-pushed
the
feature/25-split-release-creation
branch
from
c87419c to
7aa7f0e
Compare
Vincinator
approved these changes
Nov 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This PR splits the release creation from the actual package build. It means that all artifacts created during the build are first uploaded to the corresponding Github Action first and only if the build has been triggered by a Git Tag or if the built package contains the
gardenlinux0suffix, then the built artifacts are added to a newly created Github release. Other than that, the Github release creation is skipped and the artifacts can only be downloaded via the Github Action.Which issue(s) this PR fixes:
Fixes #25