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

Add GitHub Actions workflows for PyPI and CHANGELOG #136

Merged
merged 2 commits into from
Oct 10, 2024

Conversation

fellen31
Copy link
Contributor

@fellen31 fellen31 commented Oct 1, 2024

Description

I copied two of the workflows added by @dnil to Stranger, not sure how to properly setup/test that the automatic publishing works.

Added

  • Added GitHub Actions workflows for automatic publishing to PyPI on release, and keep a changelog reminder.

Changed

Fixed

How to prepare for test

  • Ssh to relevant server (depending on type of change)
  • Use stage: us
  • Paxa the environment: paxa
  • Install on stage (example for Hasta):
    bash /home/proj/production/servers/resources/hasta.scilifelab.se/update-tool-stage.sh -e S_[TOOL]-t [TOOL] -b [THIS-BRANCH-NAME] -a

How to test

  • Do ...

Expected test outcome

  • Check that ...
  • Take a screenshot and attach or copy/paste the output.

Review

  • Tests executed by
  • "Merge and deploy" approved by
    Thanks for filling in who performed the code review and the test!

This version is a

  • MAJOR - when you make incompatible API changes
  • MINOR - when you add functionality in a backwards compatible manner
  • PATCH - when you make backwards compatible bug fixes or documentation/instructions

Implementation Plan

  • Document in ...
  • Deploy this branch on ...
  • Inform to ...

@fellen31 fellen31 force-pushed the publish-to-pypi branch 2 times, most recently from d6842ce to fd4efe9 Compare October 1, 2024 09:19
@fellen31 fellen31 marked this pull request as ready for review October 1, 2024 12:38
@fellen31 fellen31 requested review from dnil and jemten October 1, 2024 12:38
@dnil
Copy link
Collaborator

dnil commented Oct 1, 2024

Sry, I missed the notification for this. Will check later if it is still open!

Copy link
Collaborator

@dnil dnil left a comment

Choose a reason for hiding this comment

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

Looks familiar and good enough to me!


## [3.8.3]

- Fixed unstable compounds order in models output ([#134](https://github.com/Clinical-Genomics/genmod/pull/134)))
- Added `six` to requirements.txt and setup.py ([#134](https://github.com/Clinical-Genomics/genmod/pull/134)))
- Fixed unstable compounds order in models output ([#134](https://github.com/Clinical-Genomics/genmod/pull/134))
Copy link
Collaborator

Choose a reason for hiding this comment

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

👍

bdist_wheel

- name: Publish distribution 📦 to PyPI
uses: pypa/gh-action-pypi-publish@release/v1
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think this will work quite well as is, based on Stranger and https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/. But if there are any problems with setting a trusted GitHub repo, remember you can back up and use a tokenized version as well. I note I'm not a PyPi admin for this repo, but there are plenty so just ask e.g. @jemten or @torbjorgen to follow the instructions in this link an all should be good.

@fellen31
Copy link
Contributor Author

Looks familiar and good enough to me!

Great, thanks for taking a look @dnil.

@fellen31 fellen31 merged commit cc7cdf0 into Clinical-Genomics:master Oct 10, 2024
2 checks passed
@fellen31 fellen31 deleted the publish-to-pypi branch October 10, 2024 06:42
dnil added a commit that referenced this pull request Oct 24, 2024
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.

2 participants