Junyong's Blog for OSD600

 In my preview blog  OSD600 -- Release 0.4.2 , I have listed six issues I am working on for my release 0.4.  I have explained what I learned and how I did for the first 3 issues, now I am going to go through the rest of the 3 issues. Issue-1449  Post header overlap (z-index) issue with hamburger menu Issue-1464   Scroll To Top button on the search page does not work in mobile version Issue-1469   Port ScrollAction from Gatsby to NextJS #1469 The  fourth PR  I have done is that  Fix Post header overlap (z-index) issue with hamburger menu. This is the simplest PR I have done so far. I used the developer tool of Chrome to check z-index of both the hamburger menu and the header. It turns out that the hamburger menu has a lower z-index than the post header.  During finding where is the z-index of each component, I learned that I can search all the code inside a big folder by right click on the folder and select "Find in Folder" in the VScode.  This feather is so powerful and I did

 OSD600 -- Release 0.4.2 In my preview blog, I have listed a couple of issues from telescope  repository that I am currently working on. They are  Issue-1424  Fix font colours in GitHub Contributor component Issue-1271  Long search results need the "Scroll to Top" component Issue-1426   Scroll To Top button doesn't move to correct position Issue-1449  Post header overlap (z-index) issue with hamburger menu Issue-1464   Scroll To Top button on the search page does not work in mobile version Issue-1469   Port ScrollAction from Gatsby to NextJS #1469 The first PR  I have done is that fix colours in Github Contributor component. I found the color property inside the link was set to text.secondary(lightBlue). I changed it to primary.contrastText(white). Then I removed the hover effect and the text-decoration to underline.  so the colour of the Contributor component from to  I also removed are an unused variable and fix a linter error in the file. I fixed a tag from  href={'

This is the last lab for the course OSD600. In this lab, we are asked to release my 1.0 version of the command line tool I have built --  urlstatuschecker , and publish it to a registry. Since my command line tool is written in node.js, I decided to publish it to " npm " registry.  I followed the documentation of c ontributing packages to the registry from npm website. Since I already finished the first few steps in the documentation, I just simply go to the package.json to modify the name and version of my repository. I modify the version number from 0.0.1 to 1.0.0, then I add a git tag to my project using the command " git tag -a v1.0.0 -m "urlstatuschecker version 1.0.0". However, My Github workflows failed when and push it to my Github.  I had a look and found out the reason is that my snapshot still has a version of 0.0.1. After I updated my snapshot then re-tag it to 1.0.1, I typed the command "npm publish" to try to publish it. Another error s