What is Merge Request / Pull Request?
Turkish: Merge Request
A merge request asks teammates to review, discuss, and approve branch changes before they are merged into a main code line.
What is a Merge Request?
A merge request is a review request opened when a developer wants to bring changes from a separate branch into the main code line. GitLab commonly uses the term merge request, while GitHub and Bitbucket usually say pull request; the workflow goal is the same.
How Does It Work?
A developer first works on a feature branch. When changes are pushed, the merge request shows file diffs, commit history, test results, and automated quality checks. Teammates can comment, request changes, or approve. Repository rules may block the merge until required approvals and CI checks pass.
Why Does It Matter?
A merge request makes more than syntax visible. It exposes design decisions, security implications, data migrations, and future maintenance cost. Small, focused requests are easier to review. Larger changes should include context, screenshots, testing notes, and a rollback plan.
Code review usually happens inside the merge request. A good review process is not only about catching defects; it also builds shared ownership of the codebase.
Related Terms
Code review checks code changes before merge so teams catch logic errors, security gaps, and maintainability issues early.
Feature BranchA feature branch keeps new work in a separate Git branch, making experiments, reviews, and merges easier to control.
GitFlowGitFlow is a Git workflow that assigns separate roles to main, develop, feature, release, and hotfix branches for controlled releases.