Home › Key concepts › Version control and pull requests

Key concept · Crawl (beginner) · the same on every platform

Version control and pull requests

Every change saved, explained and reviewed before it goes live.

What it is

Git records every change to code with who, when and why. A pull request proposes a change; others review it and automatic tests run before it is merged.

Why it matters

It is how teams work together without overwriting each other, and how you find what broke and undo it.

An example

A one-line SQL change goes through a pull request; a reviewer spots that it drops refunds.

The common mistake

Editing pipelines or prompts directly in production with no history.

Where you meet it on each platform

The idea stays the same; only the product name changes.

JobAWSAzureGoogle CloudDatabricksOpen source
Git and pull requestssave, share and review every changeGitHubGitHub or Azure ReposGitHubGitHub + Git foldersGitHub

Related ideas

Where it shows up

Part of the Crawl level on these paths: Data Engineering (running data) · AI Engineering (engineering basics) · Software Engineering (working together).