
Fork the repo on GitHub, then add your fork repo as a remote to your local cloned copy
Edit The Project to be able to send a Pull Request on the original project
To create a pull request, you need to have made your code changes on a separate branch or forked repository
Approving a pull request with required reviews
Delete a closed pull request from GitHub
A contributor is someone from the outside not on the core development team of the project that wants to contribute some changes to a project
Create and Commit changes to a New branch and send it as a pull request
The only way to open up a pull request for multiple commits is: Isolate them into their own branch. Open the pull requests from there.
You may choose to close a pull request without merging it into the upstream branch.
You can quickly find proposed changes to files project in a pull request details.
Alias creation is a common pattern found in other popular utilities like "bash" shell. Aliases are used to create shorter commands that map to longer commands.
Update your local repository with any change applied into GitHub project
Pull requests are how real teams ship code — and this course teaches you the complete workflow from scratch. Whether you're making your first open source contribution or managing multiple feature branches on a professional team, you'll learn exactly how GitHub PRs work in practice.
Master real-world pull request workflows — from your first fork to advanced multi-branch collaboration. Learn code review, open source contribution, and pro Git habits used by top engineering teams.
This course covers everything you need to work confidently with GitHub pull requests across three focused sections.
In Section 1 — GitHub Pull Requests, you'll build a complete mental model of the contribution workflow. You'll start by cloning a repository the right way, make real code changes, and submit your first pull request using the industry-standard fork workflow. Then you'll learn how to review and merge PRs, deal with closed requests, and understand how to read a project's contributor activity.
In Section 2 — Advanced Pull Request Workflow, you'll step into patterns used by professional engineering teams. You'll learn how to organize work into clean feature branches, manage several open PRs at once without losing track, resolve the complexity that comes from multiple merges, and do thorough line-by-line code reviews.
In Section 3 — GitHub Extras, you'll pick up two powerful productivity skills: building Git aliases to eliminate repetitive typing, and properly syncing your local environment after upstream pull requests land.
Pull requests are a career skill — not just a GitHub feature. Companies evaluate junior developers on how well they communicate code changes, give feedback, and collaborate through PRs. This course gives you the hands-on practice to walk into any team environment and contribute from day one.
Enroll now and start working with pull requests the way professional developers do.