Looks like the travis site build finally stopped working. The last time it worked was on a PR from 5/28/2021, but it even then it was giving confusing, mixed messages (PR failure).
I've only done a few GH actions, so I'd like some help.
The core of the current .travis.yml file boils down to: create conda environment using miniconda; build the jekyll site; deploy the site to the master branch, the branch set as the pages branch. It also has other stuff about a draft site, but I don't think that was ever operational.
I've looked at some relevant GH actions:
I don't know what role doctr plays (used in the travis CI), and whether it needs to be used in the GH action for deployment.
Note that our GitHub pages set up may be a bit out of the ordinary in having repo releases available as sites. ie, the ohw20 release is published as https://oceanhackweek.github.io/ohw20/. I assume we need to be extra careful not to mess with that.
Looks like the travis site build finally stopped working. The last time it worked was on a PR from 5/28/2021, but it even then it was giving confusing, mixed messages (PR failure).
I've only done a few GH actions, so I'd like some help.
The core of the current .travis.yml file boils down to: create conda environment using miniconda; build the jekyll site; deploy the site to the
masterbranch, the branch set as the pages branch. It also has other stuff about a draft site, but I don't think that was ever operational.I've looked at some relevant GH actions:
I don't know what role
doctrplays (used in the travis CI), and whether it needs to be used in the GH action for deployment.Note that our GitHub pages set up may be a bit out of the ordinary in having repo releases available as sites. ie, the ohw20 release is published as https://oceanhackweek.github.io/ohw20/. I assume we need to be extra careful not to mess with that.