-
Notifications
You must be signed in to change notification settings - Fork 37
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
Update project and CI #221
Conversation
uses: pypa/[email protected] | ||
with: | ||
user: __token__ | ||
password: ${{ secrets.PYPI_TOKEN }} |
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.
We could directly switch to Trusted Publisher to improve security
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.
Ah yes, can we do that in a follow up? I'm not sure how to do that with the libs org and I think the PYPI account linked is still from @balloob
Co-authored-by: Robert Resch <[email protected]>
Housekeeping PR as the repo was missing a lot of linting and CI and was a bit behind in standards.
Also switched to automatic version numbering following our other libs.
Commented out pylint and mypy in the precommit config, will fix those in follow up PR(s) as it needs a bit more work on the code and this PR would be huge otherwise.