run-workflow-step-or-job-based-on-file-changes-github-actions

[giscus[bot]]

run-workflow-step-or-job-based-on-file-changes-github-actions

How to catch errors in Boto3 with Python

https://how.wtf/run-workflow-step-or-job-based-on-file-changes-github-actions.html

[JoshMcCullough]

Thank you! Note that the "Run job ..." and "Run step ..." sections are backwards ("run job" shows an example for running steps and "run step" shows an example for running jobs).

[thomasgtaylor]

Thank you for reading! Also, great catch – I updated the article.

[jvenus99]

I had that warning when i add the if condition(if: steps.changes.outputs.infra == 'true'): Context access might be invalid

[ghost]

Thanks for reporting this. Did the flow continue to work regardless of the warning?

[trusktr]

GitHub Actions already has paths filters.

F.e.:

on:
  push:
    paths:
      - '**.js'

Why is dorny/paths-filter better? Seems like the reasoning in dorny/paths-filter is that the config can be in a single file. With GitHub Actions, the same can be done by making multiple files, right? Maybe that's even preferable.

[trusktr]

Ah, looks like GitHub Actions mentions this about their path filters:

Note

You should not use path filtering to skip workflow runs if the workflow has been configured to be required. For more information, see "Required workflows."

If a workflow is skipped due to path filtering, branch filtering, or a commit message, then checks associated with that workflow will remain in a "Pending" state. A pull request that requires those checks to be successful will be blocked from merging.

So, using dorny/paths-filter should allow the action to always run, but return early if files don't match.