tj-actions/changed-files

Health v2 · maintenance only

Adoption not part of the score

2717 stars · 333 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

A GitHub Action that detects all added, copied, modified, deleted, renamed, and type-changed files and directories relative to a target branch, commit, or previous commit. It outputs relative paths so workflows can conditionally run jobs in CI pipelines, especially in monorepos.

Use cases

• run tests only when relevant files changed in a pull request
• detect changed files in a monorepo to trigger per-package builds
• get list of modified files on push events in a GitHub workflow
• conditionally deploy services based on which directories changed
• skip CI steps when only documentation files changed
• track renamed or deleted files between commits in a workflow

When to choose

• you need change detection inside GitHub Actions workflows
• you maintain a monorepo and want conditional job execution
• you need file change lists across pull_request, push, merge_group, or release events

When to avoid

• you need to detect uncommitted changes created during the workflow run (use tj-actions/verify-changed-files)
• you are not using GitHub Actions as your CI system
• you need change detection outside of git-based repositories

Facets

plugin · maturity active

ci-cd developer-tools file-system developer-tools windows cloud github-actions change-detection monorepo pull-request continuous-integration devops automation linux macos

Member repositories

For agents

markdown · JSON · MCP: product_card(name="tj-actions/changed-files")