A Very Simple Guide to Forking on GitHub


An emoji showing a snowy owl.

This website has now been frozen!

As of 2024-03-23, owlyfans.neocities.org will no longer get updates, this means that information, links, and contact info, among other things, may be outdated or otherwise wrong by the time that you are reading this!

Please instead view the owly.fans version of this page.

A yellow warning sign.

No alt text here!

While the OwlyFans website is usually very good at using alt text, currently none of the images on this page make use of this feature. If you don't know what alt text is, then this isn't anything to worry about.

If you are new to GitHub and you want to help with a project but don't know where to start, it might seem a little confusing what to do and where to begin, so this simple guide will show the basics of how to use forking on GitHub.

Before anything, you will need to have a GitHub account.

Step 1: Find the git you want to contribute to

On your browser, go to the git that you want to make changes to, in this case, we're on this git. In simple terms, a git is a place that holds all of the code, pictures, sound, and everything else that is used in that project.

If it is for a computer game, then it will have the assets for the game, if it is a website, then it will have stuff like HTML, CSS, etc on it. Git is unique as you can see the edit history for the project and who made that change and when.

Step 2: Go fork yourself!

On the git that you want to fork, move your mouse to Fork and then to Create a new fork. Once you do this, your browser will redirect you to a new webpage that will let you decide on what the name of your fork for the project should be. A lot of the time, it's fine to just keep this all the same, so just press Create fork.

And boom. You now have your own version of the project. You can make your own changes to this and the original won't be affected at all. Think of it like printing a picture off of the Internet and drawing on it - the original won't change at all.

Step 3: Making changes

Now that you have your own version of the git, you can make changes to it. On GitHub, you can simply just drag and drop your new files to the git. You can also delete files as well by clicking on the three dots icon that will be next to Add file button that you will see when you are either in a folder or when you are in a file.

Once you are happy with your changes, there will be a box that says Commit changes, here you can give a title to your changes and write a description of it. Once happy, click on the green button.

Step 4: Making a pull request (PR)

You can now make a pull request (PR). This will send a message to the git of the original project that anyone can see. In this message, people usually write down their changes, why they should be added, and anything else important.

Click on the Pull request button. This will lead you to a new page. Now, press on New pull request.

You will once again be redirected to a new page that will show all of the changes that you made to the project. When you send in a PR, other people will also be able to see the changes that you made to the project. Once happy, press the very nice Create pull request button.

Now is your time to shine. Write about all of the changes that you made and why they should be merged (added) to the project. Once you are happy with what you have done, click the Create pull request button for a final time.

Step 5: Now you wait

Once you have sent out a new PR, the owner (and also anyone who follows the project) will get an E-Mail and a ping to say that you have sent out this request. On GitHub, there is a comment section on this page where people can talk about your pull.

If the owner likes it, they will merge it, effectively adding it to their project. If the owner does not agree with the changes, they can outright reject what you did. If they want something changed, you can fix up the code by changing it on the fork that you made. You will not have to send another pull request.

Hopefully, your changes do get added. Once they do, you will be able to see yourself be credited on the Contributors section of the original git.

Happy forking!


Want to support OwlyFans? See our NFTs!

The text is copyrighted 2021 - by Cass «Owly» Python, licensed under the FOPL-MDP. Please see humans.html for full credit and thanks. Peace and love.

τ