From 5f99ae7c6ae1e7712965823b0047bf0c976b8e1e Mon Sep 17 00:00:00 2001 From: Alistair Laing Date: Wed, 19 Dec 2018 13:23:07 +0000 Subject: [PATCH] Clarify process for deploying a pre-release Changes are needed in two different repos and the existing README does not explain this well. --- docs/contributing/publishing-a-pre-release.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/contributing/publishing-a-pre-release.md b/docs/contributing/publishing-a-pre-release.md index 44e18227f2..e1f6a56edb 100644 --- a/docs/contributing/publishing-a-pre-release.md +++ b/docs/contributing/publishing-a-pre-release.md @@ -16,8 +16,10 @@ No changes get published to npm as part of the process. 4. Run `npm run release-to-branch`. -There should now be a branch `pre-release-[your-branch-name-here]` pushed to remote, which you can install with: +There should now be a branch `pre-release-[your-branch-name-here]` pushed to the GOV.UK Frontend remote origin. + +To install this pre-release branch in another project, you can run the following command: ```bash npm install --save alphagov/govuk-frontend#pre-release-[your-branch-name-here] -``` \ No newline at end of file +```