CodeBlanks Logo Icon CodeBlanks
Login Register

What is a PR?

Learn that a pull request is a code review flow.

What is a pull request?

A pull request (PR) is a GitHub feature that proposes bringing changes from one branch into another, usually the main branch. When a PR is opened, team members can review the code, discuss changes, and decide whether to merge them. This process is called a code review.

feature-login  ---- PR ---->  main

A pull request is not a local Git command; it is a collaboration feature provided by platforms such as GitHub.

Source and target branches

When creating a PR, the source branch contains the changes. The target branch is where those changes are proposed to be added. For example, feature-login can be the source branch and main the target branch.

Base: main
Compare: feature-login

GitHub displays the commit and file differences between these branches to make review easier. Similar workflows are called merge requests on platforms such as GitLab.

Practice Define the PR direction

Write two lines defining feature-login as the source branch and main as the target branch for a pull request. Show the source branch in Compare and the target branch in Base.

Starter code

terminal
# Hedef dal

# Kaynak dal

Sample solution

terminal
# Hedef dal
Base: main

# Kaynak dal
Compare: feature-login

Expected output

Base: main
Compare: feature-login

Questions and answers

Review the lesson questions together with their answers. To test yourself, solve the lesson interactively.

1 What is the main purpose of a pull request?

  • To download a remote repository to a computer
  • To submit code changes for review and merging Correct answer
  • To delete all commits in the local repository
  • To change Git user information

Explanation: A pull request allows changes from one branch to be reviewed and evaluated before they are brought into the target branch.

2 Set the PR target branch

Question 
Base: ____
Answer 
Base: main

Explanation: The Base field identifies the target branch into which changes will be merged.

3 Pull request concepts

Term Meaning
Pull request Proposal to merge changes
Code review Team review of code
Source branch Branch containing the changes
Target branch Branch receiving the changes

All lessons in Intermediate

1 Branch management

  1. Branch list
  2. Creating a branch
  3. Deleting a branch
  4. Summary - Branch management

2 Checkout and switch

  1. git checkout
  2. git switch
  3. git restore
  4. Summary - Checkout and switch

3 Merge and rebase

  1. Merge traits
  2. What is rebase?
  3. Rebase vs merge
  4. Summary - Merge and rebase

4 Conflict resolution

  1. Conflict markers
  2. Resolving a conflict
  3. mergetool
  4. Summary - Conflict resolution

5 Stash

  1. git stash
  2. stash list
  3. pop vs apply
  4. Summary - Stash

6 Tag

  1. git tag
  2. Lightweight vs annotated
  3. Pushing tags
  4. Summary - Tag

7 Remote

  1. git remote
  2. remote add
  3. remote remove
  4. Summary - Remote

8 Fetch and pull

  1. git fetch
  2. fetch vs pull
  3. Fetch all branches
  4. Summary - Fetch and pull

9 Cherry-pick

  1. git cherry-pick
  2. Picking a single commit
  3. Conflict case
  4. Summary - Cherry-pick

10 Revert

  1. git revert
  2. revert vs reset
  3. Reverting a specific commit
  4. Summary - Revert

11 Reset

  1. git reset
  2. soft mixed hard
  3. HEAD reference
  4. Summary - Reset

12 Reflog

  1. git reflog
  2. Recovering a lost commit
  3. HEAD history
  4. Summary - Reflog

13 Pull request

  1. What is a PR?
  2. Opening a PR
  3. Reviewing a PR
  4. Summary - Pull request

14 Fork

  1. What is a fork?
  2. Fork vs clone
  3. Upstream sync
  4. Summary - Fork

15 Code review

  1. What is review?
  2. Adding comments
  3. Approving
  4. Summary - Code review

16 Issues

  1. What is an issue?
  2. Opening an issue
  3. Labels
  4. Summary - Issues

17 Actions basics

  1. What are Actions?
  2. Workflow file
  3. Trigger
  4. Summary - Actions basics

18 Release workflow

  1. Overview
  2. Tag a release
  3. Changelog
  4. Release commit
  5. Publish

19 Team repo

  1. Overview
  2. Branch strategy
  3. PR flow
  4. Resolve conflicts
  5. Merge

20 Intermediate final

  1. Branch management
  2. Rebase
  3. Conflict
  4. PR flow