Update to also publish to Azure Static Sites #2378
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… for deployment Introduce the AzureSitesEnvironment variable to manage different deployment environments (e.g., preview, canary). This change allows for more flexible and environment-specific deployments. Additionally, add steps to create a GitHub App token and use it for deploying static web apps to Azure, enhancing security and automation in the deployment process.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-river-093197403-2378.westeurope.5.azurestaticapps.net |
Add a new step to build the site with Jekyll into a different directory (`./_site2/`) and upload it as a separate artifact. This allows for parallel builds or testing different configurations without interfering with the primary build. The commented-out Jekyll build action is retained for potential future use.
…ew artifact Add a step to download the AzureDevOpsMigrationTools-Site2 artifact and update the deployment path to use the new artifact. This ensures the correct version of the site is deployed, improving the deployment process and maintaining consistency with the latest build artifacts.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-river-093197403-2378.westeurope.5.azurestaticapps.net |
Adding the `--baseurl "/"` parameter ensures that the site is built with the correct base URL, which is essential for proper linking and resource loading in the production environment. This change helps avoid issues related to incorrect paths when the site is deployed.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-river-093197403-2378.westeurope.5.azurestaticapps.net |
The baseurl parameter is set to an empty string to ensure that the site builds correctly without appending any base URL. This change is necessary to avoid potential issues with URL paths when deploying the site.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-river-093197403-2378.westeurope.5.azurestaticapps.net |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🔧 (main.yml): add AzureSitesEnvironment variable and GitHub App token for deployment
Introduce the AzureSitesEnvironment variable to manage different deployment environments (e.g., preview, canary). This change allows for more flexible and environment-specific deployments. Additionally, add steps to create a GitHub App token and use it for deploying static web apps to Azure, enhancing security and automation in the deployment process.