Lab 4

Introduction
    This weeks lab was fairly frustrating, I am not sure if it was all the environmental stressors around me this week, or if it was since I had never worked with a git remote before. Nonetheless, the work has been completed. Heres a little gif to let you know how I felt.

Picking and Filing an Issue

    For this weeks lab, I choose to work on an old friends repository. Im not sure if this is considered cheating, however, I gave my friend a call to run me through how his code works. In five minutes, I had a basic understanding of his work, and was left to study his code. Since it was not my own code, I had some difficulty reading it. I created a new branch, and started cleaning up the repository to better fit my needs.

    I created a pull request simplifying the code, however, no merge was done. I guess everyone has their own preference of how their code should look. After failing the first time, I decided to try again by creating an issue on his repository, starting a new branch, and getting to work!

Here is Niaz's Repository : https://github.com/Niaz-Ul-Haque/nlinks
Here is The First Pull Request : Cleaning Console Logs

Creating and Working on Topic Branch

    Since this repository was not the same logic as mine, I instantly knew that this repository needed some critical thinking. Niaz's structured his command line interface to have his "--good", "--bad", and "--all" optionality as the third parameter. This made things a little tricky. I had to think of a logical way to integrate my logic without jeopardizing his. 

Creating an issue on repository: https://github.com/Niaz-Ul-Haque/nlinks/issues/16

Completing the Feature

    After completing the issue at hand I created a merge request and asked Niaz to check out my repository before merging. However, Niaz seemed to not realize lab four asks us to test the pull request before merging. He just merged the pull request trusting in my abilities. As much as I was flattered by his gesture, it reminded me of a quote from the movie Chernobyl, "Trust, but verify".

    This is when everything burst into flames. I thought I finished the feature! I checked the next day only to discover that I broke his logic. This was a blessing in disguise since this allowed Niaz to learn to verify every merge before he implements it. I quickly fixed the logic and pushed a new merge. Now I'm not sure if Niaz will read my message before merging, however, he now has the chance to checkout my branch before merging.


Here is The Main Pull Request :Ignore Urls PR
Here is The Main Pull Request Fixed : Sorry Niaz
This is The Last Pull Request Updating ReadMe

Reviewing, Testing, and Merge via Remotes

I have yet to get Niaz's Pull request. I will update this later this week.
Thanks for reading my blog post.

Image for post





Comments

Post a Comment

Popular posts from this blog

Working with others

     This week our course was given the task of creating a cli command, which included our code being reviewed by one of my classmates. Initially, this gave me some anxiety as sharing my work with others is not my strongest suit. Nonetheless, I created a post asking if anyone was looking for a partner and Michael Appeared.      It turns out that having someone look over my work was much less scary than I had initially anticipated. Working with Michael was actually fun, and having the opportunity to look over someone else's work was a great learning experience for me.       With another pair of eyes looking at my code, Michael noticed errors and instructions that I was not addressing. Some instructions I had forgot to mention include the fact that my program requires bash. It did not occur to me that most of us live in a Windows Operating System. Another missing component was my Blog link in my READme. I had forgotten to include a link to my blog! As soon as Michael notified me he w
Read more

The Progress

This week I decided on a repository to work on, the telescope repository. I was excited since this was a front end development issue. I had never created my own component before, however, I have some prior experience using React. I started by creating a bottomBar component and locating where I should add this component. I located the PageBase.js, the mobile application interface, and added the component to the bottom of the page. I started by creating a div with a red background to make sure I was on the right track. since it has been a couple months that I have not worked with React, I started with the most basic tasks, such as, creating a react component, a  div element, and rendering the component I made.     After confirming that I did not break anything, I started designing the layout of the desired BottomBar. The idea was created by  agarcia-caicedo,   proposed a bottom app bar t o improve mobile usability. If you're curious on the original idea you can check out his 
Read more

We are off! V0.1

Initial Release V0.1  Our first Assignment was to create a command-line tool to check and report dead links in a file. Status code 200 would be considered "Good", 400 and 404 is "Bad", and all other status codes are considered "Unknown." My first experience creating a release was nerve racking. With no instructions on how to approach this problem, I started to brain storm ideas, and eventually started questioning my abilities. Inevitability, I chose to do my assignment in bash since it would allow me to colour my code, as well as create a command line tool. Overall, the first assignment was fairly simple to use. Simply clone or fork the repository, open up bash, and run the command. Command : ./cliCommand <filename> NOTE: This project will need Bash installed on your machine. Mac OS has bash built in, however, Windows OS may need to install Bash. Please feel free to play with codes, if you have a crazy idea, then pull request :) Usage and Features Us
Read more