Skip to content

Commit

Permalink
Remove automatic triggering of deploy step
Browse files Browse the repository at this point in the history
Description:
- Since the `govuk-ci` user isn't a member of the `gov-uk-production-deploy` GitHub group it can't deploy to the production environment
- Hence this still needs to be deployed manually by a member of the team so only trigger the workflow manually not when a new release is made
- Closes #41
  • Loading branch information
nimalank7 committed Jun 14, 2024
1 parent d37e554 commit fead5c7
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 3 deletions.
3 changes: 0 additions & 3 deletions .github/workflows/deploy.yml
Original file line number Diff line number Diff line change
Expand Up @@ -10,12 +10,9 @@ on:
required: true
type: string
default: 'main'
release:
types: [released]

jobs:
build-and-publish-image:
if: github.event_name == 'workflow_dispatch' || startsWith(github.ref_name, 'v')
name: Build and publish image
uses: alphagov/govuk-infrastructure/.github/workflows/build-and-push-image.yml@main
with:
Expand Down
5 changes: 5 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,3 +35,8 @@ They all require `GITHUB_TOKEN` as an environment variable, with at
least `repo` scope.

There is also an Apps Script to pull dependency versions into a spreadsheet.

## How to deploy

This needs manual deployment to production. Once the `release` GitHub Action has run select the `deploy` GitHub action and
under `Use workflow from` choose to deploy from the latest tag. Then enter the latest tag number into the text field.

0 comments on commit fead5c7

Please sign in to comment.