GitHub resource guide
Repositories that explain how developer tools really work.
Use primary source repositories to confirm behavior, find known bugs, compare releases, and avoid debugging from outdated snippets.
01microsoft/vscodeVS CodeThe editor source and issue tracker. Use it to verify regressions, extension-host failures, and platform-specific editor behavior.02nodejs/nodeNode.jsThe Node.js runtime source. Use it for runtime errors, module-loader behavior, release notes, and confirmed platform bugs.03python/cpythonPythonThe reference Python implementation. Use it for interpreter behavior, standard-library issues, and version-specific changes.04git/gitGitThe Git source repository. Use it for command behavior, release history, documentation, and low-level repository problems.05github/docsGitHubThe source for GitHub documentation. Use it for authentication, repositories, Actions, security, and account workflows.06actions/runnerGitHub ActionsThe official Actions runner. Use it for runner releases, job execution behavior, labels, and runner-specific failures.07vercel/next.jsNext.jsThe Next.js framework repository. Use it for routing, rendering, hydration, build, caching, and deployment-related framework issues.08facebook/reactReactThe React source and issue tracker. Use it for rendering behavior, hooks, reconciliation, server components, and release changes.09microsoft/TypeScriptTypeScriptThe TypeScript compiler repository. Use it for diagnostic behavior, language changes, compiler regressions, and type-system edge cases.10kubernetes/kubernetesKubernetesThe Kubernetes source repository. Use it for workload behavior, API changes, controller issues, and version-specific cluster bugs.
Debugging workflow
Where to look inside a repository.
README and docsConfirm supported setup, configuration, and expected behavior before changing code.
IssuesSearch the exact error and version to find confirmed bugs, workarounds, and maintainer questions.
Releases and tagsCheck whether the failure started after a version change or was fixed in a newer release.
Changelog and commitsIdentify the change that introduced, deprecated, or corrected the behavior.
Minimal reproductionsCompare your project with a maintainer-approved example or reproduction repository.
Source searchTrace the exact error string to the code path that emits it when documentation is incomplete.