Closed pkalita-lbl closed 2 months ago
@pkalita-lbl You should now have permissions to make the changes you need.
Does there need to be an update in end-user (i.e. for curators and non-technical "site maintainers") docs?
I don't think so. From a user/editor/maintainer perspective the site will build and redeploy on pushes to master
just like it used to.
You should now have permissions to make the changes you need.
Yes I do! I will take care of the settings before merging.
Fixes #507
Summary
.github/workflows/deploy.yaml
) which fetches the latest GO REF data (make _data/gorefs.yaml
) and then builds and deploys the Jekyll site.vendor
directory which is created by theruby/setup-ruby
action (https://github.com/ruby/setup-ruby?tab=readme-ov-file#bundle-config) to theexclude
list in the Jekyll config.redirect_from
in_docs/taxon-constraints.md
. I don't really understand how this was working before in the automatic Jekyll build provided by GitHub Pages. This hash caused the build to fail for me locally as well as when I tested this deployment in a fork: https://github.com/pkalita-lbl/geneontology.github.io/actions/runs/8302393139/job/22724573998#step:6:373Comments
Just before merging this we will need to update this repo's settings to change the GitHub Pages build and deploy source to GitHub Actions. I don't have permission to make that change in this repo. Maybe @kltm can do it. Here's a screenshot of the correct setting in my test fork: