Hacktoberfest: First Pull Request - Tower of Hanoi

-

This post describes the journey of Hackoberfest which encourages new people to get involved in the open-source community. I always want to participate in the open-source community but did not know how to do it. So, it was really good opportunity for me to start my first open-source contribution.

I started finding the project I can work on. There are thousands of projects on the lists but it was hard to find the properly difficult issue I can handle on. Finally, I found an issue to work on and the issue I found for the first pull request of the Hackoberfest is the following: https://github.com/ahampriyanshu/algo_ds_101/issues/697

This issue is an algorithm for the Tower of Hanoi which is a mathematical game or puzzle. It consists of three rods and some disks of different sizes, which can slide onto any rod. I asked to assign me to this issue in C# and got confirmed. 

Firstly, I searched for the algorithm of the Tower of Hanoi. I got I can create a recursive function to solve this task. Secondly, I googled the C# syntax to create functions and handle input or output. As I already have some knowledge about the C# while I learn ASP.NET, I could learn fast. The final code I wrote for this task is the image below.


I asked to enter the number of disks for the Tower of Hanoi and the function named TowerOfHanoi is the recursive function to describe the motion of the disk. It took around 1 day to be checked and get merged my code into the project but eventually, my code was merged.

I've learned a lot working on this first Hacktoberfest pull request. It was the first time communicating with a stranger for open-source collaboration. I got how to communicate, how to push my commit, and how my pull request will be handled on GitHub. It was a really good experience.

Comments

Post a Comment

Popular posts from this blog

Lab 8: Automated Testing and Continuous Integration

-
When I developed a program, it was time-consuming to test all the functions I created when I add a feature. I needed to run each feature, check whether it gives expected output or not, and check all the output. It is possible I forgot to test a feature and later on, I realize I did not test the feature. I wonder if there any ways I can do it automatically. Now, I got the way how to do that. There is automated testing for it! To begin with it, I started searching the testing framework to apply my command-line tool named url-fi. There are some testing frameworks for Node.js such as Jest, Mocha, and AVA. The testing framework I chose is  Jest  which is a testing framework developed by Facebook. I've installed Jest running 'npm install --save-dev jest' and test whether it works properly or not.  This document  is the way I followed to install the Jest testing framework. After I've installed the Jest testing framework, I worked on separating functions. As my tool contains al
Read more

Open Source Project: Lab2 (Pull Request)

-
Image
 Introduction In this lab, I practiced contributing and submitting pull requests to other repositories I don't own. Following the lab instruction , the things I plan to practice are the following: forking and cloning other projects creating branches to work on new features and fix bugs working on code I didn't write, trying to maintain the original style and not break things creating pull requests collaborating with other developers on GitHub updating my pull requests to include fixes for review comments The Project I picked for pull request ( https://github.com/lixiaoqity/testLink/pull/7 ) I looked around the classmates' open source project and picked the project named testLink. The GitHub repository link is the following:  https://github.com/lixiaoqity/testLink/pull/7 .  I picked this project because it also uses the NodeJS which I picked for my project. It was really interesting to see how code can be written differently for the same subject. When I look over the project
Read more

Project: Final

-
Introduction In this post, I will describe the summary of how I have done each stage. The purpose of this post is for wrapping up this project. The purpose of the project is the optimization of one open-source project. I need to compile, benchmark, profiling, and optimize the software. The detailed information about the project is described in the  SPO600 winter project .  Previous posts related to this project The previous posts for this project are listed below. You can read the detailed steps of how I have done each stage. Stage 1 Project Stage 1 - Compiling and Benchmark Butteraugli Stage 2 Project Stage 2 - Profiling Butteraugli Project Stage 2: Profiling (x86_64) The links for the results Project: Organize the Results Stage 3 Project Stage 3: Optimization Stage 1 Stage 1 is for building and benchmarking the performance of an open-source software package. There are some requirements for the open-source package I need to consider. Firstly, the time for testin
Read more