I'm almost Git-ting It

-

"Ahhhh okay I get it..... I think" is what I say to myself most of the time when I'm watching Prof H's lectures on Git. This week it's about remotes. They're super informative and concise! He clears up whatever uncertainty or confusions you have about the git, granted you have been practicing and experimenting with it out on your own beforehand. This week we're tasked to merge and make a pull request to a repo of one of our peers.... but WITHOUT the use of GitHub.

So you mean to tell me we're going to do all this merging, comitting, fetching, etc. all without this helpful UI that still didn't make everything about git clear? Alright fine, in the end, the only thing I can gain from this is more git knowledge and I welcome that. So I picked a repo to work on, forked it, set up an upstream and contacted my lab partner regularly regarding the code. This time I chose me-check-links, a program written by a course mate of mine Jasper Mui.



We were to write a URL ignore feature that parses https links in there to ignore in our link checking program. Lucky for me, someone else in the class had decided to add that feature to my repo, and when I was reviewing her code addition, it gave me a base to write my code logic on. I admit I used parts of her code for Jasper, but made some significant changes on my own. After a few re-reviews as per Jasper's requests, he was finally satisfied and merged my feature branch! No more pull requests with the press of a button, its all command line from here now.

Experimenting with different git methods was interesting, substituting the simple pull request feature from github that's assisted by it's intuitive UI for the sometimes-confusing (actually most of the time) command line method of merging/version control was an experience. It helped me get more familiar with git commands and not rely so much on how github has made it a million times more simple. Also being on the command line makes an barely average programmer like myself feel like a professional coder. But through a few hiccups and learning experiences, I made it work. And like I said last week, the more I learn about git, the more I realise I don't GIT IT

Link to Jasper's repo down below

me-check-links [https://github.com/Jasper-Mui/me-check-links]

Thanks for reading :)

Comments

Post a Comment

Popular posts from this blog

HacktoberFest Entry No.2

-
Image
So around last week I found a great github repo of a chrome extension that previews contents of a webpage when you hover over a link. I stumbled upon it after a suggestion from my professor about taking a look at chrome extensions for a possible repo to contribute to. I'm glad I did because this was a chrome extension that was interesting, seemed practical and had a maintainer who was keen on receiving contributions to better his program. The extension is called Survol First I had to install it and test it out first, can't just contribute to a repo meaninglessly just to force a pr. I tested the extension and liked the functionality, it was useful and is well designed. Makes it all the more exciting for me to try and contribute to it. So I read the docs and learned how the extension worked. It uses a javascript file to inject html elements through the dom and uses mousemove event to detect anchor links to request information of a page, and positions and fills the div with conten...
Read more

Lab 1 : Our First Open Source Contributions

-
So for Lab 1 our tasks were fairly simple. Find a partner to review a repo on and make contributions, no matter the scale, to their code. Be it a suggestion for their code, reporting an issue, or even fixing up small details in their readme. So through slack I partnered up with one of my coursemates  Niaz Much like me, he wrote his code in nodejs, so it was perfect since I can go through his code easier through my understanding of node. His code, though written in the same language, differed from mine a lot. For one, he didn't use yargs so he had to process the arguments manually, and secondly he didn't use fetch and opted for a module called linkinator. No problem, in fact it's an opportunity for me to understand the logic and components that he used. I forked a copy of the repo, cloned it and tested it out for myself. The code worked perfectly as intended and processed urls well. Functionally, I couldn't find find anything in the code I could identify as a flaw or imp...
Read more

Hack.... vemberfest.. PR No. 3

-
Image
OK so this is pretty long overdue (sorry Prof!) And I still have one more pull request to go and that's on me yes. BUT, this week I spent working (or should I say learning) on our course's aggregated blog website which coincidentally, our prof is making us work on this week for the lab, so I guess I got a good head start going on.  So I took on an issue that seemed pretty straight forward in the repo. It was to change the functionality of the search bar when filtered by author. Seemed pretty straightforward enough, so I went ahead, forked the repo and cloned it on my computer. Now the reading begins, the lengthy process of coding. And the fact that this was a whole website coupled with different technologies that I'm not familiar with only made it waaayyy longer, which maybe is a sign that I should have started working on this much much earlier. But that's what happens when your time management skills is hot garbage. Anyways, I spent the next few days learning about eac...
Read more