dorny/paths-filter

Conditionally run actions based on files modified by PR, feature branch or pushed commits

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 13 minutes ago
Type:Plugin / ExtensionCategory(s):CI/CD & ReleaseDevOps & Observability
Added to GitGenius on September 20th, 2026
Created on May 20th, 2020
Open Issues & Pull Requests: 36 (+0)
GitHub issues: Enabled
Number of forks: 388
Total Stargazers: 3,339 (+0)
Total Subscribers: 11 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 19
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,177 days
Stale 30+ days: 17
Stale 90+ days: 14

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Type: Question (36)
  • Type: Enhancement (16)
  • Status: In Progress (3)
  • Type: Bug (3)
  • Status: Accepted (1)
  • Status: Blocked Upstream (1)
  • Status: Revision Needed (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

paths-filter is a GitHub Actions action that conditionally executes workflows based on which files have been modified in a pull request, feature branch, or pushed commits.

The tool solves the problem of running expensive or unnecessary CI steps when only certain files change. It works by comparing file paths against user-defined filter patterns, allowing workflows to skip jobs or steps when those patterns do not match the modified files. This prevents wasted compute resources and accelerates feedback cycles when changes are isolated to specific directories or file types.

Teams should adopt this action when they maintain monorepos or projects where different subsystems have independent CI requirements. It suits any workflow where you want matrix jobs to run selectively, where you need to trigger notifications only for certain file changes, or where you want to gate deployments based on which code was modified. The action integrates directly into GitHub Actions workflows without requiring external services or additional tooling.

The project shows consistent maintenance with regular updates addressing edge cases and expanding filter pattern support. Pull requests receive timely review and feedback. Issues are actively triaged and resolved, indicating responsive engagement with user-reported problems. The codebase demonstrates attention to test coverage and documentation quality, with examples provided for common use cases.