Create a Comment Command That Redeploys the Current Commit

[CodeGat]

Background

A common use case seems to be requiring a rebuild of the HEAD Prerelease when a model component using a @git.BRANCH reference is updated. The @git.BRANCH reference is better than using a @git.TAG/@git.COMMIT reference, as the others would either require adding a temporary tag, or copying the commit hash. It's also preferable to adding a comment to the spack.yaml noting the update, because that is an update that would need to be updated.

Add a comment command that redeploys the current HEAD.

Note

As with other ChatOps methods, this will not prevent/allow merging, unless there is a way to append checks to a given commit. Specifically, if one redeployed with a model component change that broke the model, it would still be allowed to merge. Although, https://docs.github.com/en/rest/commits/statuses?apiVersion=2022-11-28#create-a-commit-status looks good... This is not the case anymore, adding checks from non-PR sources works fine, so we can prevent merging with myrotvorets/set-commit-status-action.

Workaround

• Add an empty commit, in which the message can note what was changed: git commit --allow-empty -m "Redeploying to test out new component changes"
• Comment in the spack.yaml the hash used in the components @git.BRANCH HEAD
• Use the @git.TAG reference

[CodeGat]

At the moment, I've been testing in ACCESS-NRI/ACCESS-TEST#7. It's not currently working: ACCESS-NRI/ACCESS-TEST#7 (comment)

One of the issues is the incrementing of deployment numbers - on.issue_comment considers the deployment to be on the main branch, and so our incrementing counter based on gh api /repos/access-nri/access-test/deployments --jq '[.[] | select(.ref == "$PR_BRANCH")] | length + 1' doesn't work.

We'll either have to find a different part of the deployment to hinge on instead of .ref, or find a way to associate a deployment event with the pull request, again.

[CodeGat]

Fixed it! And the deployment hinges on deployments on the PR branch + "!redeploy" comments on the PR.