Git version control system

Introduction to Drupal Git

Introduction to how the Drupal project uses Git, with links to external documentation

Setting up Git for Drupal and get GitLab access

How to install, configure, and set up Git to use with the Drupal project, and get GitLab access

• Obtaining Git access
• Configuring Git for Drupal
• Drupal Git usage policies

Using Git to contribute to Drupal

How to do various tasks with Git to contribute to improving the Drupal software and documentation

• Cloning a Drupal Git repository
• Using live previews on Drupal Core merge requests
• Merge request guidelines
• Working with patches
• Setting proper file permissions before committing files
• Making maintainer-friendly "git am" single and multi-patches
• Using git blame
• Using a Sandbox project to collaborate

Using GitLab to contribute to Drupal

How to use GitLab to contribute to improving the Drupal software and documentation

• Introduction
• Creating issue forks
• Creating merge requests
• Rebase a merge request
• Reviewing merge requests
• GitLab CI
• Editing a merge request
• Policy for use of Personal Access Tokens (PATs) and other automation
• Downloading a patch file
• Use issue forks to make core version compatibility fixes
• GitLab Frequently Asked Questions

Git for Drupal project maintainers

Git information useful for people maintaining contributed modules, themes, distributions, and Drupal core

• Committing changes
• Types of releases for full projects
• Release naming conventions
• Creating a project release
• Making a security release
• Making change logs and release notes
• Moving from a master to a version branch
• Reviewing and merging merge requests
• Troubleshooting git push errors
• Uncommon situations

Common development workflow

Feature branches, merging, deal with conflicts, database dumps and rolling back.

Git branching strategy for multiple developers

A well-structured git strategy helps prevent developers from overwriting each other's configuration.