uber-go/guide

The Uber Go Style Guide.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 25 seconds ago
Added to GitGenius on September 3rd, 2026
Created on November 10th, 2018
Open Issues & Pull Requests: 39 (+0)
GitHub issues: Enabled
Number of forks: 1,813
Total Stargazers: 17,688 (+0)
Total Subscribers: 227 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.4 days
Mean response time: 162.0 days
90th percentile: 489.7 days
Tracked items: 8

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 446 days
Stale 30+ days: 6
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

No issue events were indexed in the last 7 days.

Detailed Description

Uber Go Style Guide is a style guide that documents patterns and conventions for writing Go code.

The guide addresses the need for consistent coding standards across Go projects by capturing the patterns and conventions that Uber uses internally in its own Go codebases. It serves as a reference document that teams can adopt to maintain uniformity in code style, naming, structure, and best practices specific to the Go language.

Teams adopting this guide should do so if they value alignment with practices used at scale in a large technology organization, or if they want an established reference point for Go conventions beyond the language's own documentation. The guide suits projects where multiple developers collaborate and consistency matters, or teams building on Go at Uber who need a shared standard. The guide does not position itself against alternatives; it presents itself as a distillation of Uber's own internal practices rather than as a comparison to other style guides.

The project has attracted translations into numerous languages maintained by the Go community, indicating sustained interest and engagement with the material beyond its original English form.