<aside> 🌍 This page is public. Read about our take on public when possible, private when necessary.

</aside>

<aside> 👐 Maintained ****by @Christian Weichel and @Mike Brevoort. Contribute to this page using following our contributor flow.

</aside>

Everything lives in Git

All our code, configuration, scripts, CI pipelines, documentation, experiments, utilities; everything that makes up Gitpod lives in Git, specifically on GitHub.

At the moment we have two main repositories:

• gitpod-io/gitpod which contains the OSS and self-hosted version of Gitpod. We often refer to this repository as "core".

• gitpod-io/ops which contains private configuration for the SaaS version hosted at gitpod.io. It includes gitpod-io/gitpod as a Git submodule. We sometimes referred to this repository as "io" (because it powers gitpod.io). Nowadays "com" is the preferred short form.

There is a bunch of other repositories where we maintain other aspects of Gitpod, e.g.:

• gitpod-io/website which maintains the www.gitpod.io website
• gitpod-io/workspace-images where we maintain Gitpod's default Docker images (e.g. workspace-full)
• various templates used by Gitpod to get started with a certain technology
• gitpod-io/browser-extension the browser extension for Chrome and FireFox
• gitpod-io/gitbot which contains the automation of our Groundwork workflow based on Prow.
• gitpod-io/vscode which contains Gitpod VS Code integration

On top of that, we also maintain some of our own tools:

• gitpod-io/leeway where we maintain our build system
• gitpod-io/dazzle which contains an experimental Docker image builder used for workspace-images

Everything is built using CI

All code is built and deployed using Continuous Integration. We use werft as CI system. The werft installation at https://werft.gitpod-dev.com/ builds everything in gitpod-io/gitpod. See Tools of the Trade for more details.