ci-check

Run GitHub Actions workflows locally by parsing the YAML files in .github/workflows to extract run steps. This enables selective execution and dry-run verification of your CI logic directly on your machine.

Yes, you can test specific steps by listing executable run steps with a list command. The process skips deployment, secrets, and external actions to keep local execution safe and focused on core CI logic.

Local CI dry-run verification is the process of parsing GitHub Actions workflows to extract and validate run steps locally. It reports pass or fail for each step, allowing you to diagnose CI failures before merging.

Yes, local workflow execution detects run steps and respects the working-directory parameter specified in your GitHub Actions YAML. This ensures that commands execute in the correct project context during local testing.

When running GitHub Actions CI locally, the process intentionally skips deploy steps, secrets, and external actions. It focuses solely on validating core CI logic and run steps, so deployment sequences cannot be verified locally.

Debug flaky CI steps by parsing multiple GitHub Actions workflows to extract run steps for local execution. Running these steps locally reduces remote back-and-forth and helps isolate failing logic before merging.