From 1101da8e6274d8aeca1b28507462bdb2d22fb223 Mon Sep 17 00:00:00 2001 From: Chris Meagher Date: Tue, 17 Oct 2023 16:05:31 +0100 Subject: [PATCH] Update readme to clarify GitHub repo location and Environments availability Fixes #1 --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 576a4ac..254eb8d 100644 --- a/README.md +++ b/README.md @@ -267,11 +267,13 @@ You don't need to do anything specific to add the workflow in GitHub Actions, th #### Create an Environment 1. Sign in to [GitHub](https://github.com/) -2. Find the repo where your code has been pushed +2. Find the repo where you have pushed your code, or your fork if you forked this repo 3. Go to `Settings` -> `Environments` * Click `New environment`, name it `production`, and click `Configure environment` * Add protection rules if you wish, though it's not required +> You can read more about creating environments in the [GitHub documentation](https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#creating-an-environment). Note that there are limitations with Environments in GitHub if you are using a Free acount and your repository is private. + #### Setup permissions in Azure 1. Create a Service principal in Azure