PRs from a Fork

When you fork someone's repository on a platform like GitHub, you get a copy of the repository in your account. This is the standard way to contribute to someone else's open-source project. The steps are typically:

Fork their repo into your account
Clone your fork to your local machine
Create a new branch (let's call it your_feature)
Make changes
Commit and push changes to your fork's remote your_feature branch
Create a pull request to original_owner/repo main from your_username/repo your_feature

Then the original owner can review your changes. If they like them, they can merge the changes straight from your fork into their repository.

Click to play video

Assignment

Create and switch to a new feature branch, add_contrib, in your forked and cloned version of the megacorp repo. For example: git switch -c add_contrib.
Add a file to the contributors directory. The file should be named your_github_username.txt. (Replace your_github_username with your actual GitHub username). Add a link to your GitHub profile to the text file.
Add, and commit your changes with a commit message. For example:

add myself as a contributor

Push your change up to GitHub to an add_contrib branch in your forked repo.
Create a pull request from your add_contrib branch to the main branch of the original bootdotdev/megacorp repo.
With the pull request open, paste in a link to your public repo (not the pull request itself) and submit the tests.
Once you've passed the tests, close the pull request... we don't want your changes here!

We don't need the add_contrib branch anymore, so delete it from your local repo after switching back to main. Do NOT merge them.

Tip

To delete a branch locally while in a different branch:

git branch -D branch_name