Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trigger website rebuild when gorefs.yaml changes #2294

Merged
merged 3 commits into from
Apr 12, 2024
Merged

Conversation

pkalita-lbl
Copy link
Contributor

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 the metadata/gorefs.yaml file is changed in the master branch.

It first validates the gorefs.yaml file according to its associated schema. Theoretically any validation issues would have been caught by the qc.yaml workflow during a PR. So this is just sort of a fail-safe against someone ignoring that check or committing directly to master.

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 the geneontology/geneontology.github.io repo.

Footnotes

  1. https://docs.github.com/en/actions/using-workflows/using-github-cli-in-workflows

  2. https://cli.github.com/manual/gh_workflow_run

@pkalita-lbl pkalita-lbl requested a review from kltm April 12, 2024 23:00
@pkalita-lbl pkalita-lbl marked this pull request as draft April 12, 2024 23:01
@pkalita-lbl pkalita-lbl marked this pull request as ready for review April 12, 2024 23:05
Copy link
Member

@kltm kltm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added workflow as discussed. Seems good!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants