June 5, 2025 (Updated April 19, 2026)/1 min read

Git Pull Requests

Git Hygiene Checklist

0/4

Write meaningful commit messages

Use the imperative mood: 'Add login form' not 'Added login form'.

Pull before push

Avoid divergent histories that need merging.

Use .gitignore

Never commit build artifacts, secrets, or local config.

Branch per feature

One branch = one PR = one focused change.

Build Programming Foundations at Noble Desktop

Noble Desktop's Full-Stack Web Development Certificate teaches Git alongside the modern web stack — a must for any developer.

Pull requests are a way to discuss changes before merging them into your codebase. Let's say you're managing a project. A developer makes changes on a new branch and would like to merge that branch into the master. They can create a pull request to notify you to review their code. You can discuss the changes, and decide if you want to merge it or not.

Creating & Merging Pull Requests

GitHub and Bitbucket each have different ways to create pull requests, which they have documented on their websites.

GitHub
- Create Pull Request: help.GitHub.com/articles/creating-a-pull-request
- Merge Pull Request: help.GitHub.com/articles/merging-a-pull-request
Bitbucket
- Create & Merge Pull Request: [tinyurl.com/bitbucket-pull-request](http://tinyurl.com/bitbucket-pull-request)

Adding Commits to a Pull Request

Let's say the person reviewing the pull request wants you to make changes before they accept it. Make the changes, commit them, and push them to the branch for the pull request.

Go Beyond Git

We offer the best coding courses and bootcamps for students at all levels of experience. Classes are hands-on and students receive workbooks with step-by-step instructions through exercises with real-world applications. Check out our programming courses now: