Implement GitHub Actions Workflow for Building and Releasing Application #99
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
…in-file-reading-operations' into 96-implement-github-actions-workflow-for-building-and-releasing-application
soaressgabriel
changed the title
soaressgabriel
deleted the
96-implement-github-actions-workflow-for-building-and-releasing-application
branch
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.
Checklist:
Added tests for changed code.Updated documentation for changed code.Description
This Pull Request includes the implementation of a GitHub Actions workflow that automates the build and release process of the application. It does this by using Python for the creation of a version file, PyInstaller for the creation of an executable package, 7z for the compression of the package, and finally creates a new release in the GitHub repository with the packaged application as an asset.
Related Issue
Motivation and Context
Previously, the build and release process was a manual task that required various steps to be taken, including creating a version file, building the application, compressing the package, and creating a release on GitHub. This was time-consuming and prone to error. By automating this process, we reduce the risk of errors and make it easier and quicker to create new releases.
How Has This Been Tested
This workflow has been tested by triggering it with the creation of new tags. It successfully creates the version file, builds the application, compresses the package, and creates a new release with the package as an asset.