feat(release): Add release workflow and setup for publishing #14
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
alissonperez
force-pushed
the
feat/distutils
branch
from
d4eac81
to
f554a79
Compare
alissonperez
force-pushed
the
feat/distutils
branch
from
9a40163
to
09e77b2
Compare
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.
Ref. None
What was done?
This PR includes several changes related to the release workflow and setup for publishing. The main changes include:
How was it done?
The changes were made by adding new files and modifying existing ones. The release workflow was added in the Github actions, and the setup for publishing was done using twine. The setup.py file was created for the first time, and the package structure was refactored. Some import packages were also fixed.
How was it tested?
The changes were tested by running the release workflow and publishing to the test pypi repo. The setup.py file was also tested to ensure it works as expected. The refactored package structure and fixed import packages were tested by running the application.