Contributing To An Open Source by A First-Timer (Part 1)
Hello Fellow Codenewbies 👋
If you are self-taught, maybe you have a similar experience as mine.
As a self-taught, I only use "git" to push my own project to my own repository.
Also, other than the default (
main) branch, I never create any other branch to work with.
I always create solo projects. And my naive thought says, 'I don't see the need of creating another branch because I will push my changes directly to my
There Would Be A First Time For Everything
I never have thought of taking part in Hacktoberfest or contributing to any open-source out there simply because the idea of doing one is too overwhelming and I don't see many beginner-friendly repos for me to contribute to.
But this year - thanks to my beautiful community Virtual Coffee - I got the experience to contribute to its open-source.
(📢 Special thanks to Dan Ott for the clear written instructions and Mike Rogers for helping me out executing one when I was shaking!)
From Forking Until Committing
Fork a repo
Open the repo that we want to contribute to on GitHub and click the fork button on the top right.
Clone the repo
- Click the green "Code" button and copy the HTTPS URL.
- In the terminal, navigate to the location where we want to store the repo.
- Now it's time to use this command to clone the repo and paste the copied HTTPS URL as
git clone <repo-url>
Create a new feature branch
This branch would be our working branch where we will commit our changes and the branch that we push later on to the
git branch <branch-name>
Navigate to the feature branch
This is to make sure that we are in the branch where we will make changes before we work on it so we don't accidentally push our changes to the
git checkout <branch-name>
📝 Additional Note
There is a shortcut to create a branch and navigate it automatically to the new branch:
git checkout -b <branch-name>
- Add and commit changes
After we finish working on our changes let's add them to the staging area.
Then commit the changes.
git add .
git commit -m "The message of our changes"
We're done with all the steps from forking the repo until committing our changes.
Now let's take a coffee break before we continue to create the
Pull Request, which I will continue in the next post.
Don't push our changes before reading the next post!
This post is one of my TIL notes based on my experience contributing to Virtual Coffee's open-source.