Skip to content

CCM-16035 Update deploy worfklow#536

Open
francisco-videira-nhs wants to merge 11 commits intomainfrom
feature/CCM-16035
Open

CCM-16035 Update deploy worfklow#536
francisco-videira-nhs wants to merge 11 commits intomainfrom
feature/CCM-16035

Conversation

@francisco-videira-nhs
Copy link
Copy Markdown
Contributor

Description

Context

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

DT3-Specific Checklist

  • If I have added a new resource (SQS, Lambda, Gateway, DDB table, etc), I have created the appropriate alarms

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@francisco-videira-nhs francisco-videira-nhs requested a review from a team as a code owner April 15, 2026 12:55

- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@d6db90164ac5ed86f2b6aed7e0febac5b3c0c03e # v4
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Are we sure we want to get rid of deploying these pages? Discussion was that we are already doing this on publish, but publish doesn't deploy the docs to github pages - unless we don't want to do that anymore

type: choice
required: true
default: internal-dev
options:
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Do we still use ref?

default: dev
options:
- dev
- nonprod
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Currently there's no approvals step for nonprod deployments (as in prod). If I accidentally deploy something to nonprod via https://github.com/NHSDigital/nhs-notify-internal/actions/workflows/dispatch-deploy-static-notify-supplier-api-env.yaml (or this new deploy worflow) and it passes, it will be deployed...

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.

1 participant