# Change someone’s game: branch a showcase game and open a merge request

> Branch a public GameCrew AI game, change it yourself or with your assistant, and open a merge request. The owner plays it before and after, then merges.

- **Canonical URL:** https://gamecrew.ai/learn/branch-a-game-and-open-a-merge-request
- **Tier:** Any account
- **What you'll have at the end:** A merge request into a game’s main line with your change, checked by its engine, that its owner can play before and after and merge.

## What you need

- A GameCrew AI account: Contributor or Platform.
- A public game to change: every showcase game is public.

## Steps

1. **Find the game.** In the studio, **Explore** lists the public games, the showcase included. Open the one you want to change.
2. **Make a branch.** Press **New branch**, or open the **Branches** tab. Name it after the change (2 to 24 characters of a–z, 0–9 and -) and press **Create branch**. With an assistant: `create_branch`.

   ```
   red-boat
   ```
3. **Change the branch.** On a Platform account the branch opens on **Build**: describe the change and press **Make the change**. On the Contributor tier, your assistant works on the branch by its id with `read_file`, `edit_file` and `run_unity`.
4. **Save a version.** `save_version`. On a branch it is a quick save: it compiles and builds the game for the browser, and the version is marked not checked. `full: true` runs the full check now.
5. **Look at it the way the owner will.** `get_change` shows what the version changed: pictures of each view before and after, both play links, and the diffs.
6. **Pick a handle.** The owner sees your handle, never your email. Pick one on the **Usage** page, or with `set_handle`. Until you do, you are shown as “a contributor”.
7. **Open the merge request.** On the branch’s **Merge requests** tab, write its title in a line, add more if you like, and press **Open merge request**. With an assistant: `open_merge_request`.
8. **The owner reviews it.** The owner and the game’s crew can play it, comment on one view, asset or file, and give a verdict. Only the owner merges. Merging runs the full check first, and main gets a new version only if it passes.
9. **Answer a request for changes.** Change the branch, save again and update the merge request (**Update to v…**, or `open_merge_request` again). Notifications tell you what happened (`get_notifications`, or the bell in the studio).

## Limits

From outside a game’s crew: 1 branch of each game, 5 across the studio, 3 open merge requests per game and 10 merge requests a day. Work on a branch spends your own budget and engine minutes.

## Branch or fork?

A branch belongs to the game and goes back into it. A fork is a game of your own, where the owner allows forks (every showcase game does).

## Play one first

- **Lumen Orchard** (Three.js, plays in VR): https://gamecrew.ai/t/HoSN7eCKOHuc5i5SXlKGyFNjAHnmcPUx/?via=learn · https://gamecrew.ai/games/lumen-orchard
- **Kerbside** (Unity 6): https://gamecrew.ai/t/zqTTOEofz7kaePs8RhjVlNX4dGwytHZ1/?via=learn · https://gamecrew.ai/games/kerbside
- **Fjordline** (Unity 6): https://gamecrew.ai/t/3k5kWaqVTwbR3PoWHAH9wjss8cQeD-qp/?via=learn · https://gamecrew.ai/games/fjordline

## More

- [Build together on GameCrew AI](https://gamecrew.ai/collaborate)
- [How a crew makes a game](https://gamecrew.ai/beta)
- [Build a Godot 4 game with your coding assistant](https://gamecrew.ai/learn/godot-4-game-with-claude-code-or-cursor)
- [All tutorials](https://gamecrew.ai/learn)

## Do this now

Connect your assistant to https://play.gamecrew.ai/mcp, or tell a coding assistant: "Sign me up as a GameCrew contributor: https://gamecrew.ai/agents.md".
