Merge pull request #5663 from alphagov/issues-with-build-release-work…

…flow

Fix issues with build release workflow

.github/workflows/build-release.yml

@@ -61,11 +61,12 @@ jobs:
 
       - name: Create pull request
         env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_TOKEN: ${{ secrets.CI_PAT }}
         run: |
           git config --global user.name '${{ github.actor }}'
           git config --global user.email '${{ github.actor }}@digital.cabinet-office.gov.uk'
-          git commit -am "Release ${{ inputs.version }}"
+          git add .
+          git commit -m "Release ${{ inputs.version }}"
           git checkout -b release-${{ inputs.version }}
           git push -u origin release-${{ inputs.version }}
           gh pr create --base main --head release-${{ inputs.version }} --title "Release ${{ inputs.version }}" --body-file "release-notes-body"

docs/releasing/publishing.md

@@ -15,7 +15,7 @@ Developers should pair on releases. When remote working, it can be useful to be
 
 1. Before running the build release workflow, make sure that the [`CHANGELOG`](/CHANGELOG.md) is up to date with the latest release notes under the 'Unreleased' heading. If it isn't, do so in a separate pull request before proceeding.
 
-2. Open the actions tab on the `alphagov/govuk-frontend` repo.
+2. Open [the actions tab](https://github.com/alphagov/govuk-frontend/actions) on the `alphagov/govuk-frontend` repo.
 
 3. Select the ["RELEASE: Build release" workflow](https://github.com/alphagov/govuk-frontend/actions/workflows/build-release.yml), provide the new version of GOV.UK Frontend you are releasing and run the workflow on the `main` branch. This will build the release and generate a pull request to review the new build.