Git Remote

This week we have worked on the same project and added another new feature to allow ignoring certain links. However, this time I worked with a new partner! Since I have never worked with his project before, I spent a fair amount of time viewing his code before I began trying to add the feature. Luckily, we both used Node.js for this project, therefore it didn't take me long to get the program running and tested. While working on his project, I have ran into problems, adding a feature could be difficult, I had to make modifications to some of the original function rather than simply creating new ones. Although certain parts of the update had me stuck for a while, I was able to find all the information and resources I need from the web before I had to reach out for help in the Slack community.

Using Git for this lab was somewhat difficult, I was a bit confused when trying to follow the instructions on using git remote, it was a mess since I was putting in invalid commands. I ended up re-watching the lecture and got myself more familiarized with the commands and features git offers.

After I have added the feature, I talked to my partner within the issue that I created on his GitHub repo about this updates, however, it seemed like there were some misunderstandings in the lab instructions, therefore, we decided to use Slack to solve the problems and established common agreement on how to make changes.

This was definitely a great experience for learning to use Git more and working with different people to further develop my own knowledge and skills. If I were to do this lab again, I would definitely spent more time on trying to understanding the original code, which could've saved me a great amount of time trying to debug. I would also communicate with the project owner more while working on the codes if they're available rather than after all the implementations.

Link to Issue : https://github.com/tianlangwu/urlStatusChecker/issues/7

Merge: https://github.com/tianlangwu/urlStatusChecker/commit/b7ab995e9fa0c6802c4e5db093b8bdadcbdb377e

Comments

Post a Comment

Popular posts from this blog

Hacktoberfest -1

 This week the Hacktoberfest event has finally started and I had the chance to contribute to real open source projects. Finding an issue that I can fix took way longer than I thought it would, most of the issues were either taken or they were too complicated for a first time contributor. After a while of searching around GitHub repos with "good-first-issue" labels applied, I found a couple repositories that seemed interesting to me. One of the repositories requested for a new URL redirects in their projects, I thought this was an easy fix, but that it was more complicated than I thought it would be, the original repository had no instruction on how to run and test the application, therefore, I had to leave a comment in the issue asking for instructions. As it turns out a test must be written first before adding any code to the project, and when I ran the initial test before adding anything into the project, I was already getting testing errors, it seems like a challenging one...
Read more

Working on the Telescope Project

Image
Two weeks ago, I've had my first chance of working with the Telescope project and utilized it's back-end API to work with my DLCheck Project. In the past few days, I got more involved, played around and worked with Telescope's front-end portion. One of the issues that I found in the project repository got an idea from the Node.js webpage and requested for a React Component to display the contributors' information to thank them for their effort in developing/maintaining the Telescope project. In the beginning, I was a bit lost by reading the existing code, but luckily, the telescope project was developed using the React JS library and utilizes Material-UI framework, I have worked with a project which was also developed using the same tools during my Release 0.2 assignment, therefore, I was able to understand pieces of codes fairly quick. The new Card Component was overall not that hard to implement but it still took me a quite bit of time, I was given a custom React Hook...
Read more

Contribution Plan

Working with open source projects could be difficult, sometimes planning ahead of time could be helpful. During the past few days, I have been trying to find issues to work on, something that is challenging but could also be implemented within a couple of days, after a while of deciding what project and issues to work on, it occurred to me that there is something that I can do. While working on release 0.2 project few weeks ago, I ran into an issue in a music queuing web application GitHub repository named qasong , that is to add a clear queue button and prompts the user for confirmation. Therefore, I went ahead and added that new feature to the project. The new functionality behaves normally and works, the PR for this issue was eventually reviewed and merged, but I was not satisfied with it. While working on this issue, I was stuck on the "confirmation" part, the application was built with Material-UI components, but since I didn't have much experience with Material-UI,...
Read more