firecow/gitlab-ci-local

Tired of pushing to test your .gitlab-ci.yml?

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 58 minutes ago
Type:CLI ToolCategory(s):CI/CD & ReleaseDevOps & Observability
Added to GitGenius on September 16th, 2026
Created on January 4th, 2020
Open Issues & Pull Requests: 50 (+0)
GitHub issues: Enabled
Number of forks: 217
Total Stargazers: 4,089 (+0)
Total Subscribers: 25 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 24.5 hours
Mean response time: 28.9 days
90th percentile: 51.7 days
Tracked items: 227

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 13% of issues opened in the past year have never received a reply. 97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "nice" is answered fastest, typically in about 8 hours, while "bug" waits about 4 days. 73% of issues opened in the past year have been closed, leaving a working backlog. Three people close 87% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 32
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 318 days
Stale 30+ days: 29
Stale 90+ days: 21

Recent activity

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

Top labels

  • bug (54)
  • feature (54)
  • elaborate (26)
  • nice (13)
  • readme (4)
  • good first issue (2)
  • enhancement (1)
  • out-of-scope (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

gitlab-ci-local is a command-line tool that runs GitLab CI pipelines locally on your machine.

The tool solves the friction of testing CI/CD pipeline configurations by allowing developers to execute their .gitlab-ci.yml files locally before pushing to a repository. Rather than committing and pushing changes to test pipeline behavior, gitlab-ci-local reads your pipeline definition and runs the jobs in a local environment, typically using Docker containers to simulate the CI execution context. This approach eliminates the cycle of pushing tentative changes, waiting for remote CI to execute, and discovering configuration errors.

The tool suits developers who frequently iterate on pipeline configurations and want faster feedback during development. It works well for projects that already use GitLab CI and Docker, since it leverages Docker to containerize job execution locally. The README does not name alternative tools or make comparisons to other solutions, so no comparative guidance can be offered.

The project shows consistent maintenance with regular updates addressing user-reported issues and feature requests. Development activity demonstrates responsiveness to community feedback, with fixes and improvements being incorporated based on actual usage patterns. The codebase remains actively refined, with attention paid to edge cases and compatibility with evolving GitLab CI features.