Skip to main content

Setting up a template repository for GitHub Codespaces

You can help people get started with a project by setting up a template repository for use with GitHub Codespaces.


By setting up a template repository, you can help people get started with your framework, library, or other project in GitHub Codespaces. Users will be able to start working with your template files immediately in a cloud-based development environment, without having to worry about cloning your repository or installing tools or other dependencies. With some configuration, you will be able to set users up in a codespace with important files already open for editing, and with an application already running in a preview browser tab within the VS Code web editor.

Anyone with read access to your template repository can create a codespace from the repository's page on GitHub. You can turn any existing repository into a template, and you do not have to change any settings to allow users to create a codespace from your template repository. For more information on turning a repository into a template, see "Creating a template repository."

You can provide a link in the format to take users directly to a "Create a new codespace" page for your template.

Screenshot of the "create a new codespace" page

For example, you could provide this link in a tutorial for getting started with your framework. In your link, replace OWNER/TEMPLATE-REPO with the name of your template repository, for example monalisa/octo-template.

When someone creates a codespace from your template, the contents of your template repository will be cloned into their codespace. When the user is ready, they will be able to publish their work to a new repository on GitHub belonging to their personal account. Any usage charges for the codespace will be billed to the user who created it. For more information, see "Creating a codespace from a template."

Describe your template

If you don't have one, create a README for your template repository to describe the purpose of your template and how to get started with it. For more information, see "About READMEs."

A short description of your template is displayed on the "Create a new codespace" page that users land on when they follow the link. This description is taken from the Description field that you can set when you create a repository. You can edit this description at any time by navigating to the repository's page and clicking next to the About section on the right of the page.

Screenshot of the "About" section on a repository page

Add starter files

Template repositories typically contain starter files with boilerplate code so users can quickly get started with a library, framework, or other technology.

For guidance on the kinds of files to include, you can look at the starter files included in the official GitHub templates for GitHub Codespaces, as follows.

  1. Navigate to the "Your codespaces" page at

  2. To view the full list of templates, under "Explore quick start templates," click See all.

    Screenshot of the "Explore quick start templates" section, with "See all" highlighted

  3. To view the template repository that contains the files for the template, click the name of the template.

    Screenshot of the "Explore quick start templates" section, with "React" highlighted

Configure the container image

You can add dev container configuration files to your template repository to customize the development environment for people using your template with GitHub Codespaces. You can choose from a list of predefined configuration settings in Visual Studio Code, or you can create a custom configuration by writing your own devcontainer.json file. If you don't add configuration files, the default container image will be used. For more information, see "Introduction to dev containers" and "Add a dev container configuration to your repository."

Note: When users create codespaces from the Use this template button in a template repository, they will not be given a choice between configurations. The codespace will be built based on the default configuration defined in .devcontainer/devcontainer.json, or in .devcontainer.json at the root of your repository.

You should configure your dev container with the tools and customization to give users the best experience with your template. For example, in your devcontainer.json file:

  • You can use the openFiles property to define a list of files to be opened automatically in the VS Code web client when a codespace is created from your template.
  • If your template contains files for a web application, you can make the application run automatically in the user's codespace. You can do this by using the postAttachCommand property to run a script that starts the application on a local server as soon as the VS Code web client connects to the codespace, and by setting the onAutoForward property of a port to openPreview to display the application running on that port in a simple browser embedded in the VS Code web client.

The following configuration settings for a React template will open the app.js file in the user's editor, run npm start (defined in a package.json file) to start a local server, and forward port 3000 to a preview browser tab in the codespace.

    "postAttachCommand": {
      "server": "npm start",

    "portsAttributes": {
      "3000": {
        "label": "Application",
        "onAutoForward": "openPreview"

    "customizations": {
      "codespaces": {
        "openFiles": ["src/App.js"]

For more information, see "Automatically opening files in the codespaces for a repository" and the dev containers specification on