Add semantic release support and use black formatter#9
Merged
isandyawan merged 7 commits intoOct 21, 2023
Merged
Conversation
This file contains hidden or 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
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 pull request introduces significant enhancements to the current Python package. It adds support for Semantic Release with GitHub Action to automate versioning, migrates existing build tools from deprecated
setuptoolstoPoetryfor better package management, and reformats the code using theBlackformatter for consistent styling.I have created a sample repository to demonstrate the development workflow after this PR is merged.
Changes introduced in this pull request:
Semantic Release Integration:
GitHub Action has been integrated to automate versioning based on conventional commit messages.
Migration to Poetry:
Build tools have been migrated from
setuptoolstoPoetry, providing a more modern and efficient way of managing dependencies, builds, and publishing.Code Formatting:
The codebase has been reformatted using the
Blackcode formatter to ensure a consistent and standardized coding style.This PR aims to streamline the development workflow, maintain a consistent code style, and simplify package management. It also sets the groundwork for smoother and more automated future releases.
Please note that before merging this PR:
GH_TOKENsecret variable is added with value of a GitHub personel API token with sufficient privilege, for example:a
v0.1.1tag is created and published for latest commit (b0c7133) to make sure the semantic release integration can continue from current version which already publishedWorkflow permissions (Settings > Code and automation > General > Workflow permissions) has been set to read and write permissions

PYPI_TOKENsecret variable is added with value of PyPi API tokenPlease review and provide feedback to ensure these changes are aligned with the project's goals and standards. Thank you!