Being familiar with Github is one of the prerequisites for developers. As a front-end developer, I knew I needed all the knowledge I could get to improve my skill, even if I had prior knowledge, which was the basics of GitHub; thus, when the technical writing club in the web3Ladies community announced the GitHub Workshop, I immediately knew I had to be available to attend this one.

It was a two-day-a-week schedule that lasted three weeks. The classes were held via Google Meet, and there were other web3ladies in attendance.

Our First Meeting

On the first day of the workshop, the tutor and everyone in attendance introduced themselves.The tutor was engaging and friendly, which kept the session moving and everyone involved in some way. Aside from that, he made sure that everyone with a laptop had hands-on practice while he was teaching us.

He introduced us to github and the things we could do with it, particularly contributing to open source. We all had a basic understanding of what Github and open source are by the end of the first class.

The tutor announced that the Github workshop would focus on document-based contributions to open-source (since the workshop is for the technical writing club ). It was a successful first meeting.

Through the workshop

Because of how the tutor explained things during the first meeting, I began looking forward to the next time we had classes. Aside from that, having a tutor who is patient enough to let you practice through a virtual workshop is invaluable, and I wouldn't trade it for the world.

The next time we met, we started with a check-in routine for everyone, which lifts the mood of the class before teaching begins. Before this workshop, I had heard about open-source but had no experience with it. This was an excellent opportunity to learn about open-source.

Through the workshop, the tutor taught us the following topics:

• Forking a project on Github

• Cloning a project on Github

• Looking for open-source projects on Github

• Understanding open-source projects you want to contribute to

• Contributing to your chosen open-source project

• Committing and pushing changes to open-source projects

• Making a pull request after a contribution.

We learned all topics above in three weeks, with hands-on practice and guidance from the tutor. After each class, the tutor encourages us to go back and try out what he taught us on our own, which assisted me later in contributing to my first open source project.

The tutor's patience and willingness to repeat explanations if you didn't understand something stood out for me.

After the workshop

The tutor encouraged us to look for open-source projects to contribute to at the end of the workshop, which I did. He mentioned the annual Hacktoberfest program and how taking part in it can help you build your portfolio and get started in open source.

I chose an open-source project mentioned by the tutor during the workshop, checked out the issues, and chose one that I could understand. I commented on the issue to see if it was open to contributions. I received a response stating that it was available.

I contributed to the project by submitting a pull request. My pull request was merged, which felt good. This was how I started contributing to open-source through my Github account. Aside from contributing to an open source project, it greatly aided in the improvement of my github skills.

Conclusion

Thanks to our tutor, @dulemartins, for the in-depth workshop sessions. It was both educational and interactive and thanks to web3ladies for providing the space to develop and pick up new abilities, as well as my technical writing team lead, Udoh Osarumwense Cynthia who never gets tired of reminding us of classes, hosting calls, and always inviting us to join in order to learn and grow.

If you want to learn more about open-source and how to contribute, follow this link to a detailed article on how to find and contribute to open source.

If you're interested, you can join the web3ladies technical writing club to take advantage of additional opportunities. If you have any questions, you can contact me via Twitter or LinkedIn.. I would be happy to respond to them.

Thank you for taking the time to read my article. See you on my next article!