Skip to main content

How to communicate with other people

 

Starting...

This lab is to help students to communicate with the owner in open source world to solve the conflicts of merging their branch to remote origin. So, following the instruction, I forked one repository that I chose and create an issue to add new feature of ignoring url patterns from a file.

git clone https://github.com/StellaJung-Student/project-checkurl.git

Progressing...

Actually, The main of my task is not about the implementation above. It is just helping another classmate to help his or her task complete. Of course I also have had the part from another student so I added his repository as another remote one.


My issue on my repository is issue-11 so I typed following command.
git checkout -b issue-11 pedro/issue-11

He did great for the task but I realized that he didn't modify readme for the feature of ignoring urls so I created issue-11-fix.

git pull pedro issue-11
git checkout -b issue-11-fix pedro/issue-11

Git is actually so great since it automatically provides notifications. Once I pushed my change with the command "git push original issue-11-fix", the partner's git repository had the notification below.


After my partner checked all of my change from issue-11-fix following the command of git below,
git remote add upstream <my git repo> 
git fetch upstream
git checkout -b issue-11-fix upstream/issue-11-fix
git checkout issue-11
git merge issue-11-fix

I updated my repository from the fetch, git fetch. At that time, I didn't have to command as long as like git fetch <my partner git stream name> since I already did before. After I  changed my branch to master, simply I merged with the command git merge <partner-name>/issue-11 and pushed the code to my repository and closed the issue. 

Conclusion

To be honest, for me, understanding the concept of this git lab part  was very difficult so I had to ask a lot of questions about this concept. Thankfully, in the slack, there are not only my professor also very helpful classmate, Tony, helping a lot of parts to be more cleared. As a result, now I have known how to use fetch, pull, push and communicate with other remote repository without PR, which is a great journey. I believe this way will be used for a developer having a trouble in fixing a bug or implementing some business logic. The reason I am thinking this way is that the owner, let say helper, created the issue-fix and tried to add something to be better and let the partner review the code and re-push the code to their repository and finally the owner fetched the repo and after making sure that everything looked good, the issue was closed by the owner.

P.S. fetch is very important to update and clone to your repository to the remote one. 

Labels:

Comments

Post a Comment

Popular posts from this blog

Getting more difficult?

  Release 0.2.4 Now I am at almost the end of release 0.2 and I chose the telescope as the final contribution. To be honest, this is huge, well organized and great project and it is first time to take a look. Unlike my previous assignment during the previous terms, there are tons of what I have never seen. First, docker compose is great and the document for contribution is very clear. Of course, I had no idea when read it first, but every time as my professor mentioned, there was a great guy, helper?, helping me a lot to set up the project. Although I had no idea about Elastic-search and Redis-cache server, I was happy to take a time to look though the codes and to understand. Again, trying to understand an issue is always hard for me and sometimes I am really not happy when somebody does not understand my question. This happened again. The reason why I attached the picture is that I am still confused about the whole process of this project especially about why frontend didn't get ...
Post a Comment
Read more

Working with telescope

   Starting... This lab is to help students to communicate with a big project, telescope, and understanding how to handle with the set it up. There were a lot of trouble since many of technologies are new for me such as docker, docker-compose, elastic search ladis, pino, and so on. Let's jump in the big project . Progressing... The first step I took is to install wsl 2. It is not very difficult since microsoft provides good instruction, link . Although the telescope provides very good instruction,   here , It was not really easy for me to get a concept and set it up successfully. Therefore, I needed to ask a lot of questions on slack, telescope channel. Some helped me a lot and explained so much and finally I got it work successfully.  After my server was working locally, I didn't have any issue to get the response from the url, http://localhost:3000/posts.  To communicate with the local server, actually I needed to change my code a lot since I wanted to sp...
Post a Comment
Read more

Finally, release my first open source.

  Starting... This lab is to release my product to install easily. Instead of cloning or downloading and setting it up manually, it provides a lot of convenience for users to install it. I chose NPM since I used nodejs. NPM  is a great site to help develpers to release their git repository in the site.  Progressing... First, I signed up on npmjs.com and logged in the site on the console to release my repository. I had to set up a lot of things like 'npm init', modifying readme and package.json to be ready.  Second, I tried to release my repository by the command, 'npm publish --access public'. Unfortunately, the name, http-parser, was already taken, so I needed to change my name. I chose my name as http-checker and tried to release it again. At this time, I got 403, forbidden error. I spent a lot of time to figure out but it was actually due to not verified account. Once I got the verified email account, finally, I got the release version of my repository. Here is my...
Post a Comment
Read more