Ø

CHABOT.DEV — A FIELD JOURNAL — VOLUME I, NO. 4

09    PLATFORMS   ✣

GitHub as a Developer Relations Platform.

GitHub is not only the world's dominant code-hosting platform. It is also a primary DevRel surface — for content distribution, community engagement, discovery, and credibility. Most modern developer-product companies treat GitHub as one…

ENTRY · 3 MIN · 680 WORDS

GitHub is not only the world’s dominant code-hosting platform. It is also a primary DevRel surface — for content distribution, community engagement, discovery, and credibility. Most modern developer-product companies treat GitHub as one of their top three DevRel channels.

Scale (2024–2026)

  • 150M+ developers registered globally.
  • Hundreds of millions of repositories.
  • TypeScript overtook JavaScript and Python as the most-used language on GitHub in August 2025, per Octoverse — attributed partly to AI agent-assisted coding favouring typed languages.
  • The platform itself. Microsoft-owned since 2018; the platform’s strategic direction is integrated with broader Microsoft developer-product strategy.

DevRel surfaces inside GitHub

GitHub is a multi-product platform with several distinct surfaces that DevRel teams use:

Repositories

  • The fundamental unit. A company’s open-source repositories are often its most credibility-bearing content surfaces.
  • README discipline matters. A clear README, with badges, quick-start, and links, drives first impressions.
  • Releases page. Used as a changelog and announcement venue.

Issues

  • Bug reports and feature requests. Public issues are a DevRel surface — how a company responds (or doesn’t) shapes its reputation.
  • Labels and templates. Mature OSS projects use issue templates to triage effectively.

Pull Requests

  • Demonstrate engineering quality. PR discussions, review comments, and merge patterns are observable; demonstrate craft.
  • External contributors. PRs from community members are a leading indicator of community health.

Discussions

  • Launched 2020. Replaces some of the function of separate forums (Discourse) for many projects.
  • Strengths. Lives where the code lives; no separate signup; integrates with issues.
  • Used by. Most large open-source projects, including Next.js, Astro, Supabase, and many AI projects.

Sponsors

  • Launched 2019. Allows direct financial sponsorship of maintainers and projects.
  • Significance. Provides a structured way for DevRel programs to sponsor relevant maintainers (a more authentic alternative to traditional advertising).

Actions

  • CI/CD as a DevRel surface. Companies whose products have GitHub Actions integrations gain visibility through the Marketplace.

Codespaces

  • Cloud development environments launched ~2020.
  • DevRel application. “Click to try” workflows where a docs page opens a fully configured environment via Codespaces.

Marketplace

  • GitHub Marketplace lists Actions, Apps, and integrations; another distribution channel for developer products.

Pages

  • GitHub Pages still hosts many docs sites, especially for open-source projects.

Stars, forks, watchers

  • Star counts are widely treated as proxy metrics for popularity, but with substantial caveats — see ../04-metrics/vanity-metrics.md.
  • Fork counts indicate broader usage and modification.
  • Watcher counts indicate sustained engagement.

DevRel programs operated by GitHub itself

GitHub maintains substantial DevRel infrastructure around its own platform:

  • GitHub Stars — Recognition program for the most influential GitHub-using developers.
  • GitHub Campus Experts — Student leader program.
  • GitHub Universe — Annual flagship conference.
  • GitHub Satellite — Regional events.
  • GitHub Octoverse — Annual state-of-software-development report; one of the most-cited annual industry references.
  • GitHub Education — Free Pro access for students; Student Developer Pack.
  • GitHub Copilot DevRel — Dedicated team for Copilot adoption.

See ../05-companies/devtools-platforms.md for detail.

How DevRel teams use GitHub strategically

  • Treat your repos as marketing surfaces. A well-maintained README is an asset.
  • Respond to issues quickly. Time-to-first-response on GitHub issues is a leading sentiment indicator.
  • Run a public roadmap on GitHub. Several developer products use GitHub Projects as a public roadmap (Vercel, Supabase historically).
  • Open-source your samples. A /examples repo with deployable samples is one of the highest-leverage DevRel artefacts.
  • Curate awesome lists. Many companies sponsor or maintain “awesome-X” curated lists for their domain.
  • Sponsor relevant maintainers. Especially those whose libraries integrate with your product.

GitHub Copilot and the agentic shift

Copilot’s evolution from autocomplete (2021) to agentic coding (2024–2026) has substantially reshaped what GitHub means for DevRel:

  • Documentation must be AI-readable because Copilot ingests it.
  • MCP servers and Copilot integrations are new DevRel surfaces.
  • Agent experience (AX) — the experience AI agents have using your APIs and docs — is increasingly a deliberate DevRel concern.

See also