ci: refactor notification email templates#462
Merged
Roopan-Microsoft merged 3 commits intomainfrom Mar 24, 2026
Merged
Conversation
Roopan-Microsoft
approved these changes
Mar 24, 2026
|
🎉 This PR is included in version 1.11.6 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or 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
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.
Purpose
This pull request updates the deployment orchestrator and notification workflows to improve the handling and reporting of the cleanup stage, streamline input validation, and enhance notification emails with clearer status summaries and configuration details. The changes make the workflows more robust and the notifications more informative for recipients.
Workflow enhancements and cleanup handling:
cleanup-deploymentjob to.github/workflows/deploy-orchestrator.yml, which runs after deployment and E2E tests, and passes its result to the notification job. The notification job now depends on cleanup completion.cleanup_resultis now passed as an input to the notification workflow, and its value is used to determine and display the cleanup status in notification emails. (.github/workflows/deploy-orchestrator.ymlR132-L137, F63f414cL61R61)Notification and reporting improvements:
Input validation and workflow simplification:
e2e_test_resultnot required and defaultingcleanup_resultto 'skipped'. (.github/workflows/job-send-notification.ymlL36-R37, F63f414cL61R61)Does this introduce a breaking change?
Golden Path Validation
Deployment Validation