Skip to content

fix: Restrict deploy workflow to manual trigger only#849

Merged
Prajwal-Microsoft merged 1 commit into
mainfrom
psl-workflow-fix
May 15, 2026
Merged

fix: Restrict deploy workflow to manual trigger only#849
Prajwal-Microsoft merged 1 commit into
mainfrom
psl-workflow-fix

Conversation

@Yamini-Microsoft
Copy link
Copy Markdown
Contributor

Summary

Removes push and/or pull_request triggers from the deploy workflow (azure-dev.yml). The workflow now only runs via workflow_dispatch (manual trigger).

Why

The workflow runs azd up which provisions Azure resources. Auto-triggering on every push/PR causes unintended resource provisioning without cleanup, leading to orphaned resource groups and unnecessary costs.

Remove push trigger to prevent automatic resource provisioning.
The workflow now only runs via workflow_dispatch.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the GitHub Actions deploy workflow to prevent automatic Azure provisioning by removing the push trigger, leaving the workflow runnable only via workflow_dispatch (manual invocation). This aligns with the repo’s operational needs since the workflow runs azd up, which can create/modify Azure resources and incur cost if run unintentionally.

Changes:

  • Removed the push trigger (including branch/path filters) from .github/workflows/azure-dev.yml.
  • Kept workflow_dispatch as the sole workflow trigger.

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

@Prajwal-Microsoft Prajwal-Microsoft merged commit 5a76906 into main May 15, 2026
8 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 2.5.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants