Background:
I have one GitHub repo for a product which is deployed to multiple separate Azure web App Services. In the deployment centre (via the web portal) for each app service, I accepted the suggestion to create a workflow yml file, so that changes committed to the repo will trigger a redeployment. I believe this is achieved with GitHub Actions
This is useful to trigger redeployment when committing code changes to the main branch, however I am encountering an undesirable consequence of this setup:
Question:
Is there some way that I can prevent the addition of new yml workflow files to the repo from triggering redeployment?
What I tried:
What I expected to happen:
What actually resulted:
Given that my workflow .yml files are all added to the path .github/workflows/ by Azure, I was able to solve the problem by editing this section of the workflow .yml file from:
on:
push:
branches:
- thisbranch
workflow_dispatch:
To:
on:
push:
branches:
- thisbranch
paths-ignore:
- '.github/workflows/**'
workflow_dispatch: