Following our brief chat on BOSC Discord, I thought I would offer some help in switching from Travis CI to GitHub Actions. We've made this change in the @nf_core community because GitHub Actions is automatically enabled for new GitHub repositories and forks and doesn't require users to do any additional steps. In our experience it's also faster and gives a nicer interface in GitHub pull-requests.
Whilst I was here, I also added a workflow to build the Docker image and publish it to the GitHub Package Registry. The same logic applies here - this should work out of the box for any users, and keeps all resources attached to a single repository.
Please note that I have not run any of the original Travis CI tests or used bionitio previously, so this code is purely written by reading what you already had set up. It will probably need some work to (a) get it working and (b) get it to fit in to the bionitio community nicely for other languages.
Hi! Great talk at BOSC2020 🎉
Following our brief chat on BOSC Discord, I thought I would offer some help in switching from Travis CI to GitHub Actions. We've made this change in the @nf_core community because GitHub Actions is automatically enabled for new GitHub repositories and forks and doesn't require users to do any additional steps. In our experience it's also faster and gives a nicer interface in GitHub pull-requests.
Whilst I was here, I also added a workflow to build the Docker image and publish it to the GitHub Package Registry. The same logic applies here - this should work out of the box for any users, and keeps all resources attached to a single repository.
Please note that I have not run any of the original Travis CI tests or used bionitio previously, so this code is purely written by reading what you already had set up. It will probably need some work to (a) get it working and (b) get it to fit in to the bionitio community nicely for other languages.
I hope this helps!
Phil