Merging Branches

Lab 3 of the OSD-600 course provided a great opportunity to practice using Git and GitHub, beginning of the assignment was a huge mess, I was forgetting to switch between branches and one of the new features  took me quite a while to complete because of how the previous version of the DLCheck project code was implemented, I ended up having to make some changes to the previous existing code instead of simply adding new code.

After a bit of playing around with Git and re-watching lectures to refamiliarize myself with the commands, it all became very clear to me how branches work and how to utilize various git commands, such as git log, git checkout, git status etc.

For this lab, two new features were added to the tool, one of them being allowing command line arguments such as --good, --bad, -all to be passed to filter the output by the URL's response status code. 



The other feature is to check the environment variable CLICOLOR before displaying the URLs back to the screen, if the value CLICOLOR is 0, colored output will be disabled, if CLICOLOR's value is 1, colored output is allowed. At first, I wasn't sure how this could be done in Node.js, but luckily I was able to find a tutorial on it on YouTube which guided me through the process of implementing this feature.

After the implementation of those features, I have followed the instructions and merged the branches with the main branch smoothly without any problems. Aside from adding new features, I have also looked at the feedbacks given by the community (Professor and Classmates) and updated some of the problematic codes and documentations.

Links:

Repo: https://github.com/Wei-J-Huang/dlcheck

Issue 12: https://github.com/Wei-J-Huang/dlcheck/issues/12

Issue 13: https://github.com/Wei-J-Huang/dlcheck/issues/13

Merge for issue 12: https://github.com/Wei-J-Huang/dlcheck/commit/8775371348a41288fcd976caab03a92fecf2dbc3?branch=8775371348a41288fcd976caab03a92fecf2dbc3&diff=unified

Merge for issue 13: https://github.com/Wei-J-Huang/dlcheck/commit/6f4b9f0705e9eadf29e19af4add886b5baa960b9

Comments

Post a Comment

Popular posts from this blog

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

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

Using Code Formatter and Linter

This week I was introduced to automated code formatting and linter to check for mistakes in code, I have heard of those tools before but never used them until this week. Those tools assisted me to maintain the code structure and readability, using those tools resulted in huge differences between the original project and "fixed project". To install Prettier, I followed their official installation instructions, which can be found here , and I did the same to install ESLint . There was a small problem that I ran into when I ran "eslint file.js" command, the system warmed that "eslint" is not a valid command, this was eventually solved by installing the eslint-cli, which was not mentioned in the official instructions. After I finished the set ups and configurated the tools, I ran the "script npx prettier --write ." to automate the formatting, this changed hundreds of lines in my .js files, I wasn't really surprised by this because I have always t...
Read more