Do I have to push the YML to master branch for the action to be executed?

I’ve a private project where master is deploying to production through a different CI system. So I can’t push to master without running a deploy to production which is not an option.

I’ve pushed this workflow to development-kubernetes branch but nothing is appearing in the Actions tab.

on:
  push:
    branches:
      - master
      - release
      - development
      - development-kubernetes
    paths:
      - 'build/CENSORED-client*'
      - 'CENSORED.Client/*'

name: CENSORED-client

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2

      - name: Azure Login
        uses: azure/login@v1
        with:
          creds: ${{ secrets.AZURE_CREDENTIALS }}

      - name: Azure CLI script
        uses: azure/CLI@v1
        with:
          azcliversion: 2.0.72
          inlineScript: $GITHUB_WORKSPACE/deploy-script.sh CENSORED-client $GITHUB_SHA

I pushed the same file to the master branch of a different repository and I can see the new workflow in the actions tab.

Did that push also change any of the files matched by your paths list? Because if not that’s your reason right there. :wink:

I added the workflow YML itself to the list of files matched in the path list and worked. Thank you! :smiley:

1 Like