Migrate CI from Travis to Github Actions #71
Conversation
|
@josemduarte Sorry to ping you on old biojava-legacy stuff! For some reason Github Actions didn't pick up and run CI on this pull request. I just did the same thing on a repository I own ten minutes ago and GA picked it up right away. heuermh/velocity-cli#18 Have I missed some configuration setting? Thanks in advance |
|
Yes setting github actions CI can be complicated. It took me forever to get it running in biojava... Did you check the protected branch settings? That's also necessary for PRs to run the tests I believe. This is how it looks like in biojava: |
|
If I look there it says no status checks found. I am guessing it is a permissions issue, pull request from a fork against an organizational repository ... although I also enabled Github Actions for our bigdatagenomics repositories recently and didn't run into this. |
That's something I also encountered and struggled with. They weren't there but eventually the available status checks appeared. My theory is that the system becomes aware of them only when the CI pipeline has actually run somewhere else (e.g. in a push to master). |
|
Hmm, that's also what I was thinking. I'll try merging this pull request and see if that kicks anything. |
|
The Deploy Snapshot workflow was triggered on merge https://github.com/biojava/biojava-legacy/actions/runs/1477681785 Guess I'll need to find some bug to fix so that I can create a new pull request 😉 |
Fixes #70