> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tempo.new/llms.txt
> Use this file to discover all available pages before exploring further.

# Merge an Existing Canvas

> Bring a canvas that lives on another branch into the branch you're working on.

# Merge an Existing Canvas

A canvas is a folder of code under `tempo/designs/` in your repository, so it lives on a git branch like any other file. A branch only shows the canvases that were committed to it. If a teammate built a canvas on their branch, or you made one in another workspace, your branch won't have it until it's merged in.

There are three ways to bring a canvas over. Pick the one that matches where the canvas is.

***

## The canvas is already in a pull request

This is the usual case: someone made the canvas on their branch and opened a pull request with **Create PR**.

1. Merge that pull request into your default branch (for example `main`).
2. In your workspace, update your branch from the default branch. Ask Tempo's chat:

> [!TIP]
>
> **Prompt to send in Tempo:**
>
> ```
> Merge the latest main into this branch.
> ```

The canvas now shows up in **Canvases** and in the new-chat canvas list for your branch.

***

## Copy one canvas from another branch

Use this when you want a single canvas from a branch without merging everything else on it.

> [!TIP]
>
> **Prompt to send in Tempo:**
>
> ```
> Copy the canvas folder tempo/designs/canvases/<canvas-name> from the branch
> <other-branch> into this branch, then commit it.
> ```

Tempo copies the canvas folder, including its storyboards, as a commit on your branch. If the canvas imports components that only exist on the other branch, ask Tempo to bring those files over too, or merge the whole branch instead.

***

## Just open it where it is

You don't have to merge a canvas to look at it or keep working on it. Open **Canvases** in the left navigation, pick the branch in the browser, and open the canvas. Tempo opens it in **Home** in a workspace on that canvas's branch, creating the workspace if you don't have one. The workspace you were in is left as it was.

***

## When to use which

| You want to… | Do this |
| - | - |
| Build on a teammate's finished canvas | Merge their pull request, then update your branch |
| Reuse one canvas in a different branch | Copy the canvas folder from the other branch |
| Review or continue work on a canvas | Open it from **Canvases** on its own branch |

> [!NOTE]
>
> Merging and copying are ordinary git changes. They appear in your workspace's **Changes**, and they go to review with the rest of your branch when you open a pull request.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.