paths-filter
Paths Changes Filter allows to run GitHub Actions workflows conditionally based on pull requests, feature branches, or files modified by the submitted commit. It eliminates the lack of built-in GitHub road filters that do not operate at the individual business or step level, thus saving time and resources in monorepo structures. Pull request supports a variety of workflow scenarios, including feature branch, merge queue, and main branches.
dorny · DevOps / Build / Infra
Common commercial products in this category: GitHub Actions, CircleCI, Atlassian Bamboo
- According to the modified files, you run slow integration tests or distributions only for the respective components.
- You detect pull requests, feature branches, and file changes via the submitted commit.
- You save time and resources on monorepo projects using GitHub REST API or go commands.
- • NeutralGitHub Issue
Filter files for a PR based on changes since the last commit
“I have been using the package to run specific actions based on changes against the base branch, but to avoid the actions running every single push I was wondering if it was possible to run only based on the previous commit for a PR. Example workflow: - New PR is created -…”
- • NeutralGitHub Issue
[error] The process '/usr/bin/git' failed with exit code 128
“I'm unable to get my `changes` job to run which uses `paths-filter` within it. It always fails with the following error: ![Screenshot 2020-07-16 11 09 05]( My workflow looks like this: ``` name: Deploy API server on: push: branches: [master] jobs: changes: runs-on: ubuntu-latest…”