-
Notifications
You must be signed in to change notification settings - Fork 27
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
Move build to sbt-github-actions #296
Comments
Some extra notes if you want to work on it @amsayk:
We'll need to add secrets to the repo, but that can be done after everything is set up in the code. Probably the best starting point is to copy-paste the changes from kubukoz/slick-effect@149ea9c . In general, this will require some changes to the build e.g. moving |
Hi @kubukoz, I'll take work on this. Thanks for the tips. |
I will work on the site on a separate pull request. |
Closed in #299. Many thanks! |
Travis CI has had its time, but I've had a better experience with GitHub Actions and Daniel's generative sbt plugin. We should migrate the build to use that instead.
The obvious issue with the migration that I can foresee is the microsite, which might require some extra dependencies like sass & jekyll. It's probably a good idea to start without the site and then we'll add it once we have the Actions working.
Some inspiration:
The text was updated successfully, but these errors were encountered: