feat(build): Add version file and release based on file #34
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
|
I'm making some corrections and will make an improvement available soon. |
c7c66b0 to
572d07e
Compare
572d07e to
780ee26
Compare
|
@r3kzi You can review |
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.
This change adds the ability to release a Docker image from an existing version file update in the repository.
When the VERSION file is changed and merged into the master branch, the Github action is triggered to generate a new version of the Docker image, create a release and tag on GitHub, and make a snapshot bump for the next version of the application.
Inspired by: https://medium.com/@ignatovich.dm/implementing-a-release-process-with-github-actions-for-docker-image-management-and-rollback-9e385bb7c99a
C/c: @r3kzi