> For the complete documentation index, see [llms.txt](https://docs.cloudback.it/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudback.it/gitlab.md). # GitLab Cloudback for GitLab - setup, backup contents, restore, and pricing for GitLab project backups. Cloudback provides secure, automated backups for your GitLab projects, including repository content, issues, merge requests, labels, milestones, boards, and project metadata. ## Getting Started * [Installation Guide](/gitlab/installation-guide.md) - Step-by-step guide to connecting your GitLab account to Cloudback * [First Backup Walkthrough](/gitlab/first-backup-walkthrough.md) - Learn how to monitor and manage your first backup * [Restore](/gitlab/restore.md) - How to restore GitLab data from a backup ## Key Features for GitLab * **Repository backups**: Git repository content via bare clone (all branches, tags, and refs) * **Project Metadata**: Issues, merge requests, labels, milestones, boards, and more * **OAuth Integration**: Connect your GitLab account through GitLab's secure OAuth flow * **Cross-Platform Restore**: Restore GitLab projects to GitHub or vice versa ## What Gets Backed Up Cloudback backs up your GitLab projects, including repository content, issues, merge requests, labels, milestones, boards, and associated metadata. For a complete list of what's included, see [GitLab Backup Contents](/gitlab/backup-contents.md). ## Pricing GitLab backups use a per-project pricing model - each project consumes 1 unit. See [GitLab Pricing](/gitlab/pricing.md) for plans and details. --- # 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.cloudback.it/gitlab.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.