ci: convert from automatic to manual releases #37
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
paoloyx
requested review from
robbenti,
maocorte,
bigmoby and
lorenzodagostinoradicalbit
|
Releases will be created by manually invoking the workflow, see: https://docs.github.com/en/actions/using-workflows/manually-running-a-workflow |
|
@robbenti @bigmoby @lorenzodagostinoradicalbit can you please review this one? Thanks! |
lorenzodagostinoradicalbit
approved these changes
Jun 27, 2024
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.
We're at the beginning of our journey and we think that, in this situation, an automatic way of releasing is not the proper one. A manual release gives us the certainty of creating bullet-proof releases, while in the meantime we work hard to improve all the rest (i.e. testing, qa etc. etc.) as automatic releases will anyway be our standard in the next future.