Starting...
I had no idea how I could contribute, create, and fix an issue. I was afraid of messing up other's repository. Anyway, I have to try in order to follow the curriculum. I forked and cloned one of my classmates' repository. It was my first time to test codes implemented by someone else.
Reading...
I went through the codes and tried to find any issue, were not easy at all. Anyway, the first issue I found is a very tiny thing: 'let' keyword although that never changed. It would be better to use 'const' keyword I think.
Another issue is that the person did not use .gitignore . Although, I think it is not a big issue in here, It would be also better to node_modules in .gitignore to prevent accidently upload huge setting file to git.
Lastly, It seems to have similar issues that I had already in my source code. It was about the wrong way like using async or promise functions as sync functions. The call of each urls tried to request a call to get status code one by one.
Thus, I tried to fix that issue too. I created another branch and tried use Promise.all instead of for statement and it turned out that the result was faster than before.
The issue link and Forked repository
After fixed the issues, there was the button displayed for pull request so I clicked it and another step came out for it.
Once I created pull request, I realized the git checked all of things if there was a conflict or not. Of course, I also met the conflict and I fixed. Now, I know why people like git a lot especially for team project.
Although the owner of the repository refused to merge my fixed code, it was a great experience and now I know how I can contribute my work in open source world.
Comments
Post a Comment