eradman/entr

Run arbitrary commands when files change

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 19 minutes ago
Added to GitGenius on September 11th, 2026
Created on March 27th, 2018
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 124
Total Stargazers: 5,680 (+0)
Total Subscribers: 38 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 91 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

entr is a file-watching utility that runs arbitrary commands when files change.

The tool solves the problem of manually re-running commands during development by monitoring the filesystem and automatically triggering actions when watched files are modified. It works by leveraging platform-specific file monitoring mechanisms—inotify on Linux and kqueue on BSD and macOS—to detect changes and execute user-specified commands in response. This approach eliminates the need for manual intervention during iterative development workflows.

The tool suits developers who want to automate repetitive command execution during coding, testing, or building. It works well for test automation, where tests can run automatically whenever source files change, and for build workflows where recompilation or asset processing should trigger on file modifications. The project is particularly valuable for developers working in Unix-like environments who prefer a lightweight, command-line-based solution that integrates with existing shell scripts and build systems.

The project shows consistent maintenance with regular updates addressing bug fixes and platform compatibility. Development activity demonstrates responsiveness to user-reported issues and incremental improvements to core functionality. The codebase maintains focus on its core responsibility of file monitoring and command execution without scope creep into unrelated features.