bahdotsh/wrkflw

Validate and Run GitHub Actions locally.

View on GitHub ↗Jump to charts ↓

bahdotsh/wrkflw has 3k+ stars and 70+ forks on GitHub, is written in Rust, and was last pushed on Sep 8, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 20th, 2026
Created on March 29th, 2025
Open Issues & Pull Requests: 15 (+0)
GitHub issues: Enabled
Number of forks: 74
Total Stargazers: 3,332 (+0)
Total Subscribers: 15 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.9 days
Mean response time: 44.3 days
90th percentile: 197.9 days
Tracked items: 41

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 106 days
Stale 30+ days: 10
Stale 90+ days: 6

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

Sign in to see which issues are moving.
Sign in

Detailed Description

WRKFLW is a command-line tool for validating and executing GitHub Actions workflows locally.

The tool addresses the friction of testing GitHub Actions workflows by allowing developers to run and validate them on their machine before pushing to GitHub. It works by parsing workflow YAML files, emulating the GitHub Actions runtime environment, and executing jobs in Docker, Podman, or a sandboxed secure emulation mode without containers. The tool includes an interactive terminal UI with tabs for workflows, execution visualization, directed acyclic graphs, logs, trigger configuration, and secrets management.

WRKFLW suits developers who want faster feedback loops on workflow changes and teams that need to validate complex CI/CD pipelines locally. The tool is particularly valuable for testing composite actions, reusable workflows, matrix builds, and expression evaluation before committing. It supports multiple execution backends, allowing users to choose between containerized execution and container-free sandboxed emulation. The project includes a secrets management system with multiple providers including environment variables, files, Vault, and cloud providers, with AES-256-GCM encrypted storage. Watch mode enables automatic rerun on file changes with trigger-aware filtering to skip irrelevant workflows. The README notes that Windows and macOS runners are mapped to container images rather than native runners, and that service containers, GitHub encrypted secrets, and concurrency groups are not yet supported.

The project shows active development with regular feature additions and refinement of existing capabilities. The codebase demonstrates attention to user experience through the interactive TUI and thoughtful command-line design with strict validation modes that prevent silent failures. Development includes comprehensive support for GitHub Actions semantics including job dependency resolution, artifact handling, matrix expansion, and expression evaluation. The project maintains clear documentation of unsupported features and breaking changes, indicating a mature approach to managing scope and user expectations.