summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoe Carstairs <65492573+Sycamost@users.noreply.github.com>2023-11-18 18:06:02 +0000
committerGitHub <noreply@github.com>2023-11-18 18:06:02 +0000
commitc842fa9c4922cc439be96d7a5f4809b19af049bf (patch)
tree17ff40d75143aeba044db5b8e96872f899f27468
parent5258761f460eb15d8a14ef8cb5c98fa15c31976a (diff)
Specifies upstream branch in README where salient
-rw-r--r--README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/README.md b/README.md
index 956f255..f24a853 100644
--- a/README.md
+++ b/README.md
@@ -35,12 +35,12 @@ git clone https://github.com/Sycamost/lallans-wabsteid-astro.git \
2. Make a suitably named branch on your fork.
3. Make your desired changes (see sections below for common cases).
4. Commit and push them on your branch.
-5. Make a Pull Request to merge your changes into `deployment-staging`.
+5. Make a Pull Request to merge your changes into `Sycamost/deployment-staging`.
6. A code owner (probably the Scots Language Society Webmaster) will review your Pull Request, ask
- for any necessary changes, and when satisfied, merge it into `deployment-staging`. (This will
+ for any necessary changes, and when satisfied, merge it into `Sycamost/deployment-staging`. (This will
update the [staging deployment](#cicd) on
[staging.scotsleidassocie.org](https://staging.scotsleidassocie.org).)
-7. Code owners will merge `deployment-staging` into `deployment-production` at their discretion.
+7. Code owners will merge `Sycamost/deployment-staging` into `Sycamost/deployment-production` at their discretion.
(This will update the production deployment on
[scotsleidassocie.org](https://scotsleidassocie.org).)