--- title: "Git, GitHub, GitLab: Version Control for Drupal Projects" lang: en type: knowledge canonical: https://www.arocom.de/en/knowledge/development/git alternate: https://www.arocom.de/wissen/entwicklung/git author: "Axel Roth" last_updated: 2026-07-29 --- # Git, GitHub, GitLab: Version Control for Drupal Projects Git is the version control system that holds code together in every professional Drupal project. GitHub and GitLab complement Git with hosting, CI/CD pipelines and code reviews. Since 2012, arocom has relied on Git-based workflows in over 160 Drupal projects and uses GitLab for automated testing, deployment and quality assurance. Without structured version control, every Drupal project becomes a risk from the second developer onward. ## Git, GitHub, GitLab: Version Control for Drupal Projects Every change to your Drupal code creates a new version. Without version control, you don't know who changed what when, why an update broke the site or how to restore yesterday's state. Git solves this problem. GitHub and GitLab turn it into team collaboration. The question is not whether you need Git. The question is whether your Git workflow fits your project. ## Why Git Is Indispensable in Drupal Projects Git is a distributed version control system. Every developer has a complete copy of the repository on their machine. This means: no single point of failure, full offline capability and a complete history of every code change. In Drupal projects, multiple developers work on custom modules, theme customizations and configurations. Without a Git branching strategy, changes overwrite each other. With a clear strategy (feature branches, pull requests, code reviews), every change remains traceable and reversible. At arocom, we version not only code but also Drupal configurations via Configuration Management. This makes the entire project history reproducible. ## GitHub vs. GitLab: What Fits Your Project? GitHub and GitLab are platforms that host Git repositories and extend them with features like CI/CD, issue tracking and code reviews. The difference lies in the details. GitHub is the largest open-source platform. The Drupal community uses it extensively. GitHub Actions offer flexible CI/CD pipelines. GitLab offers an integrated DevOps platform: repository, CI/CD, container registry, monitoring in one tool. GitLab can be self-hosted, giving full control over your own data. arocom uses GitLab for client projects: the integrated CI/CD pipeline automatically runs code quality checks, security scans and tests before code reaches the live environment. Self-hosting guarantees data sovereignty for our clients. ## Git Workflow in Practice: How arocom Works A good Git workflow for Drupal projects includes: Feature branches: every requirement is developed in its own branch. The main branch stays stable. Merge requests with code review: no code reaches the main branch without review by a second developer. Automated tests: CI/CD pipelines check coding standards with every push, run tests and build the application. Configuration management: Drupal configurations are exported, versioned and synchronized between environments via Git. This workflow is not overhead but investment protection. Our [Drupal development](https://www.arocom.de/en/services/development) across over 160 projects since 2012 shows it: teams that work cleanly with Git deliver faster and with fewer errors. ### Your next step Want to know if your current development workflow is future-proof? The [Drupal Future Check](https://www.arocom.de/en/future-check) analyzes your code quality, versioning and deployment processes, among other things. **From arocom projects:** - Drupal as a dashboard platform? For marego it was exactly the right choice: editable data structures, granular roles, integrated Excel/PDF pipelines. The tool now consolidates reporting that used to live in five different tools. - For [d&b audiotechnik](https://www.arocom.de/en/references/db-audiotechnik) (Backnang) we built several configurators, process tools, and intranet solutions on/with Drupal, the architecture we put in place back in 2018 still holds today without refactoring and keeps up with every new major version. - [A clean Git workflow for your Drupal project?](https://www.arocom.de/en/contact) ### What is Git? Git is a distributed version control system that records every change to the source code and makes it traceable. "Git" is not an acronym but a proper name. Every developer holds a full copy of the entire history locally, with no single point of failure. ### Do we need Git for small Drupal projects too? Yes. Even for small projects, Git protects against data loss, makes changes traceable and enables clean deployments. The setup effort is minimal, the benefit noticeable from the first module update. ### What is the difference between Git and GitHub? Git is the version control system that runs locally on your machine. GitHub is a hosting platform that provides Git repositories on the web and extends them with features like pull requests, issues and CI/CD. ### Why does arocom use GitLab instead of GitHub? GitLab offers an integrated DevOps platform with a self-hosting option. This gives our clients full data sovereignty. The built-in CI/CD pipeline automates code quality checks and deployments in one tool. ### Can we migrate our existing repository to arocom? Yes. Git repositories can be migrated between platforms without losing history. As part of an agency switch or Future Check, we take over existing repositories and set up the workflow. ## Read more - [DevOps for Drupal](https://www.arocom.de/en/knowledge/development/devops): How CI/CD pipelines automate the deployment process - [Deployment Strategies](https://www.arocom.de/en/knowledge/development/deployment): Getting code safely to the live environment - [Project Management for Web Projects](https://www.arocom.de/en/knowledge/development/project-management): How arocom structures Drupal projects