Git basics: Contributing to open source

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
Search for a command to run...

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
No comments yet. Be the first to comment.
In this series we'll cover some basic, but very important topics in Git, GitHub and Open source
I'm sure this happens to everyone sometimes. You accidentally pushed a file with secrets or a password that shouldn't have gotten into the Git history. In the following example, I "accidentally" pushed my .env file to Git simply because I forgot to a...
Most of you know me for my consistency, a golden arrow in my blog series. I've written 1000 articles in 1008 days! Almost an article a day, and my honeymoon was the only holiday I ever took. I'm super proud of this achievement; it has been a fantasti...

It's not the first time I'll be talking about community. I think it's an essential aspect of any successful tool. This shows in my previous explorations of Astro, Medusa, and now Vendure as well. All these products thrive in a super open, welcoming, ...

The cool part about Vendure is how easy it is to set up and how abstract each layer is. Basically, we get the following elements: External database Server Worker Admin UI Frontend While this is amazing, it also brings a bit of complexity when it co...

The previous article looked at customizing Vendure on a data and process level. In this article, we'll look at customizing emails, as they are often a big part of a webshop system. We'll be looking at two different layers of customization for customi...

Even though Vendure is a pretty significant project out of the box, in some cases, we might want to go in and modify some elements to work to our specific use case. In this article, I'll take a high-level look at some elements we can customize within...

In the previous article, we looked at how you can create pull requests. We can put these in action when contributing to open source.
In this article, we'll go through the following steps.
By the end, we'll have contributed to an open-source project 🎉
Before we can start contributing to open source, we first have to find a project we wish to work on.
You might have a project in mind. If not, you can use these tools to find a good first issue to get started with.
Don't forget to comment on the issue if you can pick this up. To make sure someone else is not working on it already.
Once the ticket is assigned to you, you can start working on it.
In that repo, click the "Fork" button to create your fork for this project.

That copies the repo to your profile, so you can work on it without interfering with the original one.

Then you can set up this project locally and make sure you can run it on your system.
The simplest way is to clone the project and follow the steps in the readme.
Then make the change you discussed in the initial issue.
Some bigger repo's come with a contributing.md file. Keep an eye out for those or any specific contributing guidelines.
Once you are done, make sure to create a new branch for your local version of this project and commit the changes to that one.
This branch should now show up in your version of the forked project like so:

If you click that big green button we see above saying "Compare and Pull request", we open a PR to the original repo.

Make sure you fill out the template as the project provides it. Once you are happy with it, you can submit the PR.
Give the team some time to review it, as they might be swamped with PRs.
And there you go, you now contributed to open source! Great feeling, right?
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter