Technology
GitHub
GitHub is where the site lives. Pull requests, previews, and a history you can audit. We do not keep the real copy on a studio machine.
What it is
GitHub is Microsoft's home for git: repositories, pull requests, Actions, Packages, Codespaces, and the social layer where open source actually lives. Kubernetes, Next.js, React, and Linux's mirrors sit here. So does almost every product team's private code.
It is not only hosting. It is review, CI, issues (or the link to Linear), and the URL you put in a handover. If the repo is not yours, the product is not yours.
What it does
Teams use GitHub to store code, review changes, run checks, ship Actions, and publish packages. Auth to preview environments often starts with a GitHub user. Open source is the public face. Private repos are the work.
We build on a repository you own. Actions are documented. We do not keep the source of truth on a studio account.
Why we use it
The repository is the product you take home.
One repo for the app. A client who merged the first copy change. A history that explained a bug. Org, not a freelance account. Access is a seat, not a favour. The handover is a transfer of the repo, not a ZIP.
A zip file is not a product. A repository is.
Built on it
Microsoft
Owns GitHub and uses it across VS Code, TypeScript, and Azure samples.
A huge open-source presence, from Angular to Kubernetes-related work.
Vercel
Next.js is developed in public on GitHub.
Meta
React and React Native are GitHub projects.
Almost every engineering team
If they write software in this decade, they have a GitHub org or a mirror.
Tell us what needs to ship.
You use a working prototype before the production build goes ahead.