Skip to content
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

Create GitHub Action to automatic publish to PyPI #411

Closed
wants to merge 9 commits into from

Conversation

fredgrub
Copy link
Contributor

@fredgrub fredgrub commented Nov 1, 2023

This branch is a continuation of PR #408 and was rebased from the one proposed on #409, so it has to wait to be merged into next. So I'll leave it as a draft.

You can check out a working version of it on https://github.com/pipreqsxp/pipreqs/actions/runs/6723169654 and the result of the release on https://test.pypi.org/project/pipreqs-build-test/.

For it to work on the main repository, you should configure the API token from PyPI on GitHub (check https://docs.github.com/pt/actions/security-guides/using-secrets-in-github-actions).

@codecov-commenter
Copy link

codecov-commenter commented Nov 1, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (fb4560c) 90.07% compared to head (a88d1f1) 90.07%.
Report is 1 commits behind head on next.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@           Coverage Diff           @@
##             next     #411   +/-   ##
=======================================
  Coverage   90.07%   90.07%           
=======================================
  Files           2        2           
  Lines         262      262           
=======================================
  Hits          236      236           
  Misses         26       26           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

add workflow for automatic deploy on pypi
@fredgrub fredgrub marked this pull request as ready for review November 8, 2023 18:38
@fredgrub
Copy link
Contributor Author

fredgrub commented Nov 8, 2023

@alan-barzilay I just rebased this branch with next and it's ready to be merged.

Copy link
Collaborator

@alan-barzilay alan-barzilay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fredgrub what about updating the package version?

- When the version field of `pyproject.toml` changes, after the changes have been committed, a tag is created with `git tag` that refers to the new version.
- It's necessary to configure the `git-hooks' directory `git config core.hooksPath .git-hooks`.
@fredgrub
Copy link
Contributor Author

fredgrub commented Dec 3, 2023

I will be closing this PR. I ended up using it as tests and the commit history is quite disorganized. I will leave it as validation of the correctness of the workflow.

@fredgrub fredgrub closed this Dec 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants