With #Hacktoberfest coming up, I wanted to put out a quick thread to hopefully save someone the trouble of having to look up several things in order to successfully contribute to opensource for the first time!
The following thread will give you everything you need to start!
👇
Firstly, if you want to participate in Hacktoberfest as part of your first opensource experience, you can sign up here, it's totally free and super awesome imo!
Next, you're going to want to find a project that you are comfortable contributing to based on your skills.
You can use the GitHub search to look for specific things.
You can actually search for open issues labeled for Hacktoberfest on @github!
The "issue" is what you will be attempting to contribute to and fix/add!
Once you find a project and issue you are comfortable with, mention it in a comment to the project owners, so they can "assign" the issue to you.
Once you've commented, not it's time to fork the repo!! Sounds way cooler (to me at least) than it probably is, but it will create a fork in your repositories under your account.
This will create a copy under your account and include all original files and branches.
Once you've forked the repo, it's time to dive into your favorite CLI, I use terminator on Linux!
Once there, you want to navigate to the folder you will be working from and clone the repo with this command!
Next, we need our own "branch", this will allow you to work on your solution in your own space, You need to also add an "upstream" so you keep up to date.
Now in this case I made a test file to give an example, but once you update changes or add features, you will commit as you would your own project, except you push to your branch.
git push origin new_branch(name you used)
Now when you goto your repo, you will find a compare and pull request button on GitHub!
This will allow you to see your changes vs the original as well as open your pull request!
Once you've added all the code and checked that your new added feature or fix is functional, you will open your pull request and send it over with some details on what you fixed/added!
Now your pull request will be reviewed by the owner/maintainer of the original repo. They will check it for a few things, and either approve it or add a change request asking you to update something.
If this happens, make changes and push them to your branch for another review!
Once everything is approved, the owner/maintainer will merge your branch into the original files, and you will have closed the issue and successfully contributed to your opensource project!
Celebrate and then find another one :)
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Wow! 3000 amazing people from all walks of life follow me on here.
I’m so thankful, and instead of the usual thank you, I’d like to acknowledge some amazing people who have influenced me on my coding journey! As well as some accounts that deserve some more attention!
@anniebombanie_ gets first mention, she is an amazing dev, but beyond that an incredible and encouraging person who isn’t afraid to be authentic even as she grows! @jackdomleo7 one of my first friends on here, who is a skilled dev and writer, and is awesome with feedback!
@FrancescoCiull4 who is known for his best known for his memes, but honestly is such an inspiration and so knowledgeable and uplifting! @KassandraSanch an absolute css wizard, who only encourages and always takes the time to help when asked.
I try to be as uplifting and encouraging as possible, especially when I see people taking on a new challenge like coding.
The encouragement I received from others when I started to self teach HTML and CSS was the biggest driving factor in my continuing to learn.
People often underestimate the weight of a compliment or words of encouragement. You never know how close someone might be to quitting, and that small push can keep them on track and be life changing.
I’m not saying you need to be overly positive, or comment on every single post you see, but remember that even if you aren’t an expert in the content area, you can still tell someone good job, or compliment work you like.
I’ve been asked a few times how I got the confidence to approach people about freelancing a lot lately.
Especially since my stack really only consist of HTML/CSS and a little #JavaScript .
Honestly, approaching my first client was a super intimidating experience
🧵👇🏻
I have years of work experience, and my job has given me an ability to talk to anyone, anytime, anywhere which is a huge part of it.
Don’t ever underestimate how important your soft skills are. Being friendly, personable, and even having a little humor helps.
Also you need to be confident, it’s super easy to think I’m not ready yet.
@DThompsonDev told a story about how he sold his first site, sitting down at a restaurant and offering to redo their site because he tried to find their menu and it was so difficult to navigate.
A lot of people have messaged me asking how to deploy their portfolio sites after doing them for #100DaysOfCode and I figured I'd share one of the easiest methods I've found to do so.
There are many methods, but this is the one I found the simplest when I started!
🧵👇🏻
I personally love @Netlify for hosting my portfolio as well as all of my project sites. They're site is super easy to use, they have a straight forward UI, and everything all packed into one place!
Custom domain, need a form, continuous deployment, they've got it all!