From a77b0c98bfe8f6447877fec910cfb5eced0e926c Mon Sep 17 00:00:00 2001 From: Aaron Pennington Date: Fri, 2 Aug 2024 16:06:12 -0600 Subject: [PATCH] Update setting-up-the-sst-console.md (#764) quick typo fix --- _chapters/setting-up-the-sst-console.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_chapters/setting-up-the-sst-console.md b/_chapters/setting-up-the-sst-console.md index f35099e9c..4812c695a 100644 --- a/_chapters/setting-up-the-sst-console.md +++ b/_chapters/setting-up-the-sst-console.md @@ -1,4 +1,4 @@ ---- +dervived--- layout: post title: Setting up the SST Console date: 2024-07-24 00:00:00 @@ -71,7 +71,7 @@ Do the same for a **PR environment**. ![Create PR environment SST Console](/assets/part2/create-pr-environment-sst-console.png) -The two above environments tell the Console that any stage with the name `production` or starting with `pr-` should be auto-deployed to the given AWS account. By default, the stage names are dervived from the name of the branch. +The two above environments tell the Console that any stage with the name `production` or starting with `pr-` should be auto-deployed to the given AWS account. By default, the stage names are derived from the name of the branch. So if you _git push_ to a branch called `production`, the SST Console will auto-deploy that to a stage called `production`.