Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update setting-up-the-sst-console.md #764

Merged
merged 1 commit into from
Aug 2, 2024
Merged

Update setting-up-the-sst-console.md #764

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions _chapters/setting-up-the-sst-console.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
---
dervived---
layout: post
title: Setting up the SST Console
date: 2024-07-24 00:00:00
Expand Down Expand Up @@ -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`.

Expand Down