It would be great to have changes get pushed directly to update the website (in the future, to dev before prod), and so modifying the github actions to do this would be ideal.
Note that this is already partially done for the protected resources gha, but it still has some problems:
If the PR does not already exist, the PR for updating gets created just fine.
If the PR does already exists, the API returns an error and the gha fails. Also, the new commit does not automatically get added to the pull request, but there is an extra button to press on the PR before it can be merged in.
The ideal would be that the gha doesn't fail if the PR already exists, and that the PR is updated with any new commits. Perhaps API calls and a try{}catch{} statement could help with this.
Once this is solved for PR, it could be applied to the other jobs (ideally, by making a reusable workflow).
k-doering-NOAA
commented
1 year ago
It would be great to have changes get pushed directly to update the website (in the future, to dev before prod), and so modifying the github actions to do this would be ideal.
Note that this is already partially done for the protected resources gha, but it still has some problems:
The ideal would be that the gha doesn't fail if the PR already exists, and that the PR is updated with any new commits. Perhaps API calls and a try{}catch{} statement could help with this.
Once this is solved for PR, it could be applied to the other jobs (ideally, by making a reusable workflow).