Pull Request
// Definition
A proposed set of commits opened for review before merging into a shared branch — the gate where code is reviewed, CI runs, and approval happens. Called a Merge Request on GitLab. The PR is where automated tests, linting, and human review converge before code reaches `main`.
// Why it matters
The PR is QA's primary checkpoint — it's where the test suite runs against proposed changes and where a quality gate can block a merge on red. Understanding PRs means understanding where in the flow tests execute, what "required checks" gate a merge, and how review feedback loops work.
// How to test
git push -u origin feature/login-tests # open the PR on GitHub/GitLab → CI runs the suite automatically # required status checks (tests, lint, coverage) must pass before merge is enabled
// Common mistakes
- Huge PRs that are impossible to review properly (split them)
- Merging with failing or skipped required checks
- No description, so reviewers can't tell what changed or why
// Related terms
Branch
An independent line of development in a Git repository — a movable pointer to a commit, letting you work on a feature or fix in isolation without touching the main line. Branches are cheap and disposable; the typical flow is branch off `main`, commit work, open a pull request, merge back.
Commit
A saved snapshot of changes in a Git repo, with a message describing what changed and a unique hash identifying it. Commits are the atomic unit of history — each one is a revertible, reviewable point you can return to. Good commits are small and focused; the message explains why, not just what.
Quality Gate
An automated checkpoint in a build or deployment pipeline that blocks promotion if quality criteria (test pass rate, coverage threshold, security scan) aren't met.