This should be the complete CI configuration in GitHub actions for the rg-db-public workflow. There will be one final step of configuration, which is the typical addition of a GitHub secret that contains credentials for reading private repos and pushing to Billingegroup/billingegroup.github.io.
Both of these current use the same secret, which should be named GH_ACTIONS_PAT (as is laid out in the group wiki). It may be desirable for this to change in the future so that only the necessary permissions are given to each Action script.
Additionally, it may be desirable to switch the host repository/branch of the Billingegroup website (which is served via a GitHub Pages deployment), to being served from a branch within Billingegroup/rg-db-public rather than keeping it its own separate repository.
Actions:
main.yaml
Runs when a PR is created by any user, when in the PR is from a branch off of the PR's target repo (i.e., the PR has to start and end in the same repository)
publish.yaml
Runs when a push into main/master is done (e.g., when a PR is merged into main/master)
This should be the complete CI configuration in GitHub actions for the
rg-db-publicworkflow. There will be one final step of configuration, which is the typical addition of a GitHub secret that contains credentials for reading private repos and pushing toBillingegroup/billingegroup.github.io.Both of these current use the same secret, which should be named
GH_ACTIONS_PAT(as is laid out in the group wiki). It may be desirable for this to change in the future so that only the necessary permissions are given to each Action script.Additionally, it may be desirable to switch the host repository/branch of the Billingegroup website (which is served via a GitHub Pages deployment), to being served from a branch within
Billingegroup/rg-db-publicrather than keeping it its own separate repository.Actions:
main.yamlpublish.yamlmain/masteris done (e.g., when a PR is merged intomain/master)