> For the complete documentation index, see [llms.txt](https://docs.allout.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allout.game/going-all-out/collaborating-and-version-control.md). # Collaborating & Version Control There are a number of reasons to use a version control tool like Git as you develop your game * Easily backup and revert to earlier changes * Work together with other developers on your team * Easily open your project on other devices If you're unfamiliar with Git/GitHub, there is a great video tutorial series here: To get started, create a GitHub account and a repository and then authorize the All Out app to use that repository. You can authorize by heading to the Collaborate page on your game and clicking the manage GitHub connection option.
Then you're ready to select the repository you made earlier back on your games collaborate page:
When you link a Git repo, all of your editors on the collaborate page will automatically have read/write access to that repo. When they launch the editor, we'll automatically clone your repository into the editor's games folder and when you publish, they can push directly or create a pull request so you can review changes. **You can also install GitHub's desktop client to manually manage your Git changes:** Their desktop client is pretty easy to use! 1. Download GitHub Desktop: 2. Create a new repository using your game project folder 3. ![](/files/6spLXO1xVXY8hTcOzcBA) 4. Create an initial commit and publish your repository to GitHub! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.allout.game/going-all-out/collaborating-and-version-control.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.