You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/static-web-apps/named-environments.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: craigshoemaker
5
5
ms.author: cshoe
6
6
ms.service: static-web-apps
7
7
ms.topic: conceptual
8
-
ms.date: 04/27/2022
8
+
ms.date: 07/24/2023
9
9
ms.custom: template-how-to
10
10
---
11
11
@@ -15,7 +15,7 @@ You can configure your site to deploy every change to a named environment. This
15
15
16
16
## Configuration
17
17
18
-
To enable stable URL environments with named deployment environment, make the following changes to your [configuration file](configuration.md).
18
+
To enable stable URL environments with named deployment environment, make the following changes to your build configuration file.
19
19
20
20
- Set the `deployment_environment` input to a specific name on the `static-web-apps-deploy` job in GitHub action or on the AzureStaticWebApp task. This ensures all changes to your tracked branches are deployed to the named preview environment.
21
21
- List the branches you want to deploy to preview environments in the trigger array in your workflow configuration so that changes to those branches also trigger the GitHub Actions or Azure Pipelines deployment.
0 commit comments