My first Hacktoberfest Issue/PR

For my first Hacktoberfest related issue and Pull Request(PR), I was looking for a simple documentation issue to start off easy and ramp up later on. I came across one that I found interesting which was modifying an example in the README file. Since it was a README file, I thought the coding language wouldn't matter for me when I picked it to work on. I found that the example they wanted was quite similar to the method that was already implemented. So I sent a PR to update the file and the owner of the repo wanted the example to be executable. At that moment I knew it was going to be harder than I expected because the code was written in Python, which I had not used before. So starting like a beginner, I had to search for ways to compile and execute Python code. But I keep running into websites that say Python code "doesn't need to be compiled" or "automatically compiled" so that got me confused for a day or two. I ended up with downloading different software to run the program like the python extension in Visual Studio and Pycharm. Luckily for me the owner of the repo was very helpful in describing which part of my code was not working. I thought it ended pretty good because the owner merged and closed my Pull Request.

Comments

Post a Comment

Popular posts from this blog

My third Hacktoberfest 2018 Journey

This issue I created was suggested by a nice guy(Nate) who already finished 5 PR's. The idea was to increase the performance of a robot program. Instead of using the size method, a global variable would be used to keep track of the remaining robots for a quicker comparison when needed. This program was in C++ which made it very easy for me to read since that is one of my strength. The owner of the repo later told me that he didn't want to use global variables.
Read more

Helping Mozilla firefox with enabling ESLint

Image
It was an amazing experience contributing to Mozilla Firefox. The bug that I worked on: here . For new developers to help with enabling ESLint with FireFox here are the steps that I took ( Window user ) assuming you already have a bug assigned to you: Follow Mozilla Build to download and get the "Required tools" and stop at "Getting the source" Download Mercurial . Continue with Getting the Source and stop at "Build FireFox!" it's not really needed when fixing ESLint bugs and saves some time. Remove your <directory path> from `.eslintignore`. Run `./mach eslint --fix <directory path>` this will run ESLint only for the specific directory you are fixing. Note: I was told to commit 2 versions: An automatic change version and a manual change version.      6.  So at this point I did `hg commit -m "Enable ESLint for <directory path> (automatic changes)"` Since I was told I needed 2 commits I wanted to push my
Read more

Contributing to 2048 Repo cont'd

GitHub Repo: 2048 Previously, when I was working on this repository it turns out my code format was not consistent with what they had. I've noticed that they have a .clang-format file which means there should be a way for me to run it and auto format my code. After searching, I have found a couple of online formatters. When I used the online formatters it either spits back the same code format or it loads until timeout, either way I don't get what I am trying to do. I went back to searching for clang-formats and I came across a Visual Studio Code extension that allows me to use the .clang-format file. After running the clang-format on the source files, compiling errors start to arise from the .clang-format file which I have posted an issue on. After trying to fix a few of the errors the owner of the repo believes the error could be related to the VSCode extension. Apparently, they were using npm to run the clang-format file. Maybe I should have asked how they did the forma
Read more