Path Filters
ELI5 — The Vibe Check
Path Filters make your CI only run when specific files change. Changed a README? Skip the build. Changed source code? Run everything. It's like a smart doorbell that only rings when the right person shows up, not when the neighbor's cat walks by.
Real Talk
Path filters in CI/CD (paths/paths-ignore in GitHub Actions, rules:changes in GitLab CI) conditionally trigger workflows based on which files were modified. This reduces unnecessary builds and saves CI minutes by skipping irrelevant changes.
Show Me The Code
on:
push:
paths:
- 'src/**'
- 'package.json'
paths-ignore:
- '**.md'
- 'docs/**'
When You'll Hear This
"Path filters skip CI when only docs change — saves 500 runner minutes a month." / "The deploy workflow only triggers on changes to the src/ directory."
Related Terms
Branch Protection
Branch Protection puts a velvet rope around your main branch. No force pushes, no direct commits, mandatory reviews, required CI checks.
Continuous Integration
Imagine a group project where everyone keeps adding their piece to a shared Google Doc and a robot instantly proofreads the whole thing every single time.
GitHub Actions
GitHub Actions is CI/CD built right into GitHub. Push code, run tests, deploy — all from YAML files in your repo. No separate CI server needed.