Trigger website rebuild when gorefs.yaml changes #2294
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Re: #2235 -- I will close the issue manually when I'm confident this is working as expected.
Summary
These changes add a new workflow file (
.github/workflows/trigger-website-rebuild.yaml
) which runs when themetadata/gorefs.yaml
file is changed in themaster
branch.It first validates the
gorefs.yaml
file according to its associated schema. Theoretically any validation issues would have been caught by theqc.yaml
workflow during a PR. So this is just sort of a fail-safe against someone ignoring that check or committing directly tomaster
.If the validation passes we generate an access token using the GO Workflow Bot app installed in this repo. Then we use that token and the GitHub CLI1 to trigger the
deploy.yaml
workflow2 in thegeneontology/geneontology.github.io
repo.Footnotes
https://docs.github.com/en/actions/using-workflows/using-github-cli-in-workflows ↩
https://cli.github.com/manual/gh_workflow_run ↩