Skip to content

Commit 5e141c9

Browse files
Update articles/static-web-apps/publish-bicep.md
Co-authored-by: alexwolfmsft <[email protected]>
1 parent 8c2f4a9 commit 5e141c9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/static-web-apps/publish-bicep.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,7 @@ resource linkedStaticWebAppBackend 'Microsoft.Web/staticSites/linkedBackends@202
146146
After your resources are created, you'll want to deploy your application to the hosting environment. You may want to be able to deploy from both your local computer as you develop and GitHub Actions for your product workloads.
147147

148148
* **Local development environment**: Local development environment deployments are completed with [Azure Developer CLI](/azure/developer/azure-developer-cli). This tool allows you to define your deployment in an `azure.yml` file. It includes hooks to plug into the resource creation process at any point to help with deploying full stack applications, which need to know about each other at build time.
149-
* **Production environment**: The ability to deploy from a GitHub action workflow file is a built-in feature when you create your static web app. Once the file is in your repository, you can edit the file as needed. Deployment from [other source code providers](external-providers.md) is also supported.
149+
* **Production environment**: The ability to deploy from a GitHub Actions workflow file is a built-in feature when you create your static web app. Once the file is in your repository, you can edit the file as needed. Deployment from [other source code providers](external-providers.md) is also supported.
150150

151151
Learn more from a full end-to-end application, which provides resource creation and application deployment:
152152

0 commit comments

Comments
 (0)