-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: refine PyPI deployment workflow and update contributing guidelines #19
Conversation
Reviewer's Guide by SourceryThis pull request refines the PyPI deployment workflow and updates the contributing guidelines. The 'CONTRIBUTING.md' file now includes a 'Release process' section detailing the steps to create and push a new tag for automatic PyPI release. The '.github/workflows/publish.yml' file has been updated to rename the workflow and modify the tag pattern to trigger the workflow on any tag push. File-Level Changes
Tips
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @yazdipour - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟡 General issues: 1 issue found
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟡 Documentation: 2 issues found
Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
…dipour/omnivore-api-python into bugfix/redef-release-process
Closes #IssueNr
📑 Description
✅ Checks
ℹ Additional Information
Summary by Sourcery
This pull request refines the PyPI deployment workflow by updating the tag pattern for releases and enhances the contributing guidelines with a new section on the release process.