garden-io/garden

Automation for Kubernetes development and testing. Spin up production-like environments for development, testing, and CI on demand. Use the same...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 42 minutes ago
Added to GitGenius on September 19th, 2026
Created on December 3rd, 2017
Open Issues & Pull Requests: 247 (+0)
GitHub issues: Enabled
Number of forks: 296
Total Stargazers: 3,615 (+0)
Total Subscribers: 34 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 40.4 hours
Mean response time: 58.9 days
90th percentile: 111.9 days
Tracked items: 108

Most active contributors

Sign in to see contributor activity.

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 66% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 57
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 717 days
Stale 30+ days: 57
Stale 90+ days: 56

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 (80)
  • feature request (30)
  • crash (25)
  • 0.13 (8)
  • feat/templating (6)
  • priority:high (6)
  • triage/accepted (5)
  • 0.14 (4)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Garden is a DevOps automation tool for developing and testing Kubernetes applications faster.

Garden addresses the friction of maintaining separate configurations and workflows across development, testing, and CI environments. It solves this by providing a unified configuration framework based on YAML files that can be split and co-located across your codebase. The tool uses an "action graph" to declare project dependencies and track changes, enabling it to skip unnecessary builds, deployments, and test runs through smart caching. This same configuration and workflow applies consistently whether you're developing locally, running tests, or executing CI pipelines.

Teams should adopt Garden if they want to reduce the overhead of managing multiple environment configurations for Kubernetes-based projects. It suits projects where faster feedback loops matter—particularly through its sync mode, which live reloads changes to running services during development. The tool is designed for teams that value reproducibility and portability across their entire delivery pipeline, from individual developer machines through to production-like CI environments.

The project maintains active engagement with its community through a dedicated discussions forum. Development shows consistent attention to both core functionality and the developer experience around configuration and workflow automation. The codebase demonstrates ongoing refinement of the action graph system and caching mechanisms that form the foundation of the tool's performance benefits.