Forking Workflows on GitHub
Understand how to use the 'fork and pull request' model for contributing to projects where you don't have direct write access.
What is a GitHub Fork?
Imagine you want to contribute to an open-source project, but you don't have permission to directly change its code. That's where forking comes in!
A fork is simply a personal copy of someone else's GitHub repository. It lives under your own GitHub account, giving you full control to experiment and make changes without affecting the original project.
Why We Use Forking
The main reason to fork a repository is to propose changes to a project when you don't have direct write access to its original codebase.
- Safe Experimentation: Work on your copy without fear of breaking the original.
- Contribution Path: It's the standard way to suggest features or fixes to public projects.
- Personal Projects: Use a fork as a starting point for your own related project.
All lessons in this course
- Creating & Reviewing Pull Requests
- Forking Workflows on GitHub
- Code Reviews & Approvals
- Draft PRs and Pull Request Templates