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 includes several updates to the GitHub workflows and documentation for the
gpush
project. The most important changes involve the addition of a new workflow for semantic versioning, the removal of old workflows, and updates to theREADME.md
file to reflect these changes.GitHub Workflows
Semver Bump
workflow to automate semantic versioning usingsemantic-release
instead ofpython-semantic-release
. This workflow triggers on pushes to themain
branch and includes steps for checking out the code, releasing withsemantic-release
, updating the version file, and committing the changes. (.github/workflows/main-release.yaml
)Dependabot auto-merge
workflow, which was responsible for merging Dependabot pull requests automatically. (.github/workflows/pr-merge-dependabot.yaml
)Semver Bump
workflow that usedpython-semantic-release
. (.github/workflows/semver.yaml
)Documentation Updates
README.md
to reflect the switch frompython-semantic-release
tosemantic-release
for automating releases. Also updated the installation instructions to use the latest version from the GitHub repository. (README.md
)python-semantic-release
from theREADME.md
. (README.md
)Version Update
3.1.2
to3.2.0
in the_version.py
file to reflect the changes. (_version.py
)