> For the complete documentation index, see [llms.txt](https://docs.genvibe.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.genvibe.pro/integrations/github.md). # GitHub Export your GenVibe project to a GitHub repository to own the code, collaborate, and set up your own workflows. ## Connect GitHub 1. Open the GitHub connection from the integrations menu. 2. Authorize GenVibe to access your GitHub account. ## Export your project Once connected, export your project to: * A **new repository** GenVibe creates for you, or * An **existing repository** you choose. GenVibe pushes your code, and from there it's a normal Git repo — clone it, branch it, and work with it however you like. You can also **download the whole project as a zip** from the same menu if you'd rather not use GitHub. ## Why export to GitHub * **Own your code** — no lock-in; the project is standard code. * **Collaborate** — bring in teammates with normal Git workflows. * **CI/CD** — connect your own build and deploy pipelines. * **Backup** — a durable copy of your work outside GenVibe. ## Keeping things in sync GitHub export is a great checkpoint and handoff tool. For ongoing work, keep building in GenVibe and re-export when you want to update the repo. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.genvibe.pro/integrations/github.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.