Skip to content
This repository was archived by the owner on Sep 28, 2026. It is now read-only.

fix: Add posix in pre-deployment hook in azure.yaml - #176

Open
chaudhariniraj wants to merge 1 commit into
microsoft:devfrom
chaudhariniraj:dev
Open

chaudhariniraj wants to merge 1 commit into
microsoft:devfrom
chaudhariniraj:dev

Conversation

@chaudhariniraj

Copy link
Copy Markdown
Contributor

Purpose

fix: Add posix in pre-deployment hook in azure.yaml

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • ...

Other Information

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a POSIX (sh) variant of the preprovision deployment notice in azure.yaml to surface the “open an issue with logs” message in non-PowerShell environments.

Changes:

  • Added a new preprovision hook step using shell: sh that prints the deployment notice (POSIX-friendly output).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread azure.yaml
Comment on lines +29 to +33
- shell: sh
run: |
echo ""
echo " ---------------------------------------------------------------------------------------------------"
echo " Note: If deployment fails or you encounter an issue, please open an issue with the deployment logs."
@NirajC3-Microsoft

Copy link
Copy Markdown
Contributor

This PR not required now

This branch has not been deployed

No deployments
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants