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

Fix CI, move to GH #144

Closed
PGijsbers opened this issue Feb 5, 2022 · 4 comments
Closed

Fix CI, move to GH #144

PGijsbers opened this issue Feb 5, 2022 · 4 comments
Labels
Milestone

Comments

@PGijsbers
Copy link
Member

PGijsbers commented Feb 5, 2022

Continuous integration is broken. Instead of fixing it, I want to move to GH CI anyway since it's what I've come to use in other projects.

@PGijsbers PGijsbers added the CI label Feb 5, 2022
@PGijsbers PGijsbers added this to the v22.0.0 milestone Jul 27, 2022
@PGijsbers
Copy link
Member Author

PGijsbers commented Aug 1, 2022

Partial progress:

todo:

  • update and execute pre-commit with:
    • black format
    • mypy check
  • package distribution -> will not do dev releases, should install from repo
  • website build & deployment
  • test against --pre dependencies'

later:
N system tests (delayed until back-end revision)

@PGijsbers
Copy link
Member Author

Package distribution workflow is on https://github.com/PGijsbers/gama/tree/publish-ci
There are some decisions left:

  • automatically publish on push to version branch? or
  • automatically publish on tagged release? (requires manual make of github release which is again error prone, but does allow for "releases" on github) => would also require the version file to be updated, tag moved, etc. similar to AMLB.

@PGijsbers
Copy link
Member Author

I consider this done for now, I will integrate the publish action for the 22.0.0 release.

@PGijsbers
Copy link
Member Author

Closing this since #111 already covers the only automation that is not yet completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant