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

Add pre-deploy comment to PR that is updated with post-deploy info #202

Open
CodeGat opened this issue Dec 22, 2024 · 0 comments
Open

Add pre-deploy comment to PR that is updated with post-deploy info #202

CodeGat opened this issue Dec 22, 2024 · 0 comments
Labels
priority:low type:enhancement Improvements to existing features version:MINOR Doesn't require update to Model Deployment Repositories

Comments

@CodeGat
Copy link
Member

CodeGat commented Dec 22, 2024

Background

It would be nice to let users know that a deployment/redeployment is actually in progress via comment, before it happens.

This would utilize the access-nri/actions/comment action once ACCESS-NRI/actions#19 is complete.

Implementation Details

I already had part of a solution while testing:

  pre-deploy-notifier:
    name: Pre Deploy Notifier
    needs:
      - defaults
    runs-on: ubuntu-latest
    outputs:
      comment-url: ${{ steps.comment.outputs.comment-url }}
    steps:
      - name: PR Comment Notifier
        id: comment
        uses: access-nri/actions/.github/actions/comment@main
        with:
          number: ${{ inputs.pr }}
          message: |
            :rocket: [Currently Deploying](${{ env.RUN_URL }}) `${{ inputs.model }}` Prerelease as `${{ needs.defaults.outputs.prerelease-version }}` with commit ${{ needs.defaults.outputs.head-sha }}

            This comment will be updated with the status of the deployment(s).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:low type:enhancement Improvements to existing features version:MINOR Doesn't require update to Model Deployment Repositories
Projects
None yet
Development

No branches or pull requests

1 participant