A request to merge a set of code changes into a shared codebase, giving teammates a chance to review and discuss them first.
Pull requests, often called PRs and known as merge requests on some platforms, are a central part of collaborative software development with Git. A developer works on a separate branch, then opens a pull request describing what changed and why. Teammates review the changes, leave comments, and approve or request edits. Automated checks, such as tests and security scans, usually run at the same time.
For example, a developer fixing a checkout bug on an online store would open a pull request that links to the bug report, includes the fix and a new test, and explains how to verify it. Small, focused pull requests are easier to review and less likely to introduce problems than large ones that change many files at once.
The practice of having other developers examine code changes before they are merged, to catch bugs and keep quality consistent.
GitA free, open-source distributed version control system that tracks changes to code and lets many developers collaborate safely.
Version ControlA system that records changes to files over time so you can review history, collaborate, and restore earlier versions.
A step-by-step software engineering roadmap with skills, milestones and realistic timelines, plus how to land your first developer role with or without a degree.
A starter CI/CD pipeline with build, test and deploy stages, explained step by step, with sample GitHub Actions and GitLab CI configuration you can adapt.
A practical Git tutorial built around a real workday: start a repo, commit, branch, merge, sync with a remote and undo the mistakes everyone makes.