github/docs

The open-source repo for docs.github.com

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 46 minutes ago
Added to GitGenius on September 2nd, 2026
Created on May 31st, 2019
Open Issues & Pull Requests: 70 (+0)
GitHub issues: Enabled
Number of forks: 68,597
Total Stargazers: 20,792 (+0)
Total Subscribers: 3,392 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.8 hours
Mean response time: 5.8 days
90th percentile: 9.5 days
Tracked items: 1,233

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "SME reviewed" is answered fastest, typically in about 4 hours, while "fix-internally" waits about 25 hours. Only 10% of issues opened in the past year have been closed. Three people close 76% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 40
New in 7 days: 44
Closed in 7 days: 77
Avg open age: 234 days
Stale 30+ days: 10
Stale 90+ days: 8

Recent activity

Opened in 7 days: 36
Closed in 7 days: 72
Comments in 7 days: 90
Events in 7 days: 340

Top labels

  • triage (1,404)
  • invalid (1,268)
  • content (987)
  • help wanted (117)
  • copilot (82)
  • actions (78)
  • SME reviewed (66)
  • fix-internally (64)

Detailed Description

GitHub Docs is the open-source repository for GitHub's official documentation site, built with TypeScript and accepting external contributions to content.

The project solves the problem of maintaining comprehensive, accurate documentation for GitHub's products and services while enabling the community to contribute improvements and corrections. It operates through a dual-repository system: the public github/docs repository accepts external contributions to markdown content files, while the private github/docs-internal repository serves GitHub employees. Changes sync frequently between the two repositories, allowing both internal and external workflows to coexist. External contributors can modify documentation and reusable content files, but infrastructure, workflows, and site-building code remain restricted to safeguard the site's stability.

External contributors should understand that this repository has intentional limitations on what can be modified. The project accepts pull requests only for content files in the /content directory and select /data sections like reusables. Infrastructure files, workflows, and code that builds the site are not open for external modification. GitHub employees have access to a separate internal repository with fewer restrictions. The project provides contributing guidelines tailored to each contributor type, with resources for those new to open-source contribution.

The project maintains active synchronization between its public and private repositories, indicating ongoing coordination between external and internal development efforts. The dual-repository architecture with frequent syncing suggests a structured approach to managing contributions from both community members and GitHub staff. The explicit documentation of contribution boundaries and separate workflows for different contributor types reflects deliberate governance of the contribution process.