Term
Pull Request
A pull request is a proposal to merge changes from one branch into another — the standard workflow for code review and collaborative work on a repository.
Pull Request — explained in more detail
The term “pull request” (PR) comes from the GitHub world; GitLab calls the same concept a “merge request” (MR). The substance is identical: a developer asks for their branch changes to be taken into a target branch (usually main) — and reviewers check, comment, request adjustments, or approve.
Typical flow
- Create a branch off
main, commit changes locally, push the branch. - Open a pull request with a description and reference to the issue it solves.
- CI runs automatically — tests, lints, builds.
- Reviewers leave line-level comments, ask questions, suggest changes.
- The author responds with further commits in the branch.
- Once approved: merge into
main, branch gets deleted.
Why it matters
Pull requests are the bridge between individual work and team code. They enforce small, documented units, enable knowledge transfer in review, and are the seam where CI/CD plugs in.
In the AI workflow
AI-generated changes typically land as pull requests — the human checks in review what the AI proposed, instead of pushing the code straight into main.
Entdecke mehr
Git Branch
A branch is an independent line of development in a Git repository — a moving pointer to a commit, allowing parallel work without conflicts with the main code.
LexikonGit Basics for Non-Developers
What version control is, what problem Git solves, and the mental model behind it: repository, commit, branch, merge, and remote, explained plainly.
GlossarGitHub
GitHub is the largest hosting platform for Git repositories — with pull requests, code review, issues and CI/CD via GitHub Actions as the standard toolkit for software development.