New engineer who will be one serving in 100 days (2nd day)

New engineer who will be one serving in 100 days (2nd day)

Two days have already passed since I worked as an engineer.

This is yesterday's article, if you like New engineer who will be one serving in 100 days (1st day)

I want to get used to the work little by little and contribute to the team! !! And that feeling With the feeling that I don't understand anything I will write the article for the second day.

What i did today

・ Improvement of form ・ There were two improvements to the view.

Write code for the issue and send a pull request to GitHub It was a flow.

The hardest part today is Git (although I had other hardships, of course)

In the first place, when I was developing by myself, I hardly used Git, so I think I have to remember when I started working as a team.

By the way, the person who made git is the same as the person who made Linux. Is it a genius?

So today I'm focusing on Git

Git this and that

git is a version management system. This allows you to go back and forth between versions and modify them.

Basic Git commands

git init            #Initialize repository
git status          #Check the status of the repository You can check the files that have not been added
git add (File specification) #Add files to stage area
git commit          #Recorded as repository history
git log             #Check the commit log. When and who made the commit or merge
git log -p          #Check the differences made in the commit
git diff            #Show the difference between unadded files and committed ones

It's very easy, but it looks like this git commit is a one-line comment with the -m option Long comments are possible without options.

Branch There is a meaning such as branching or branch office. By branching the work, you can work independently.

git branch            #View a list of branches and the current branch
git checkout -b hoge  #Create a hoge branch and switch to the hoge branch
git checkout master   #Switch to the master branch

Regarding brunch, I would like to summarize it again this time.

GitHub pull request

Ability to have others review the code you actually wrote This is not a Git feature, but a feature provided by GitHub

It ’s not Social coding, that is, a closed world, because this function is possible. You can now share your code in a truly open way! !! It was written in the book

Refer to the git command git add → git commit → git push origin branch name If you make a pull request on GitHub after pushing with, it's OK! This is not a code, but how to use GitHub, so it is omitted.

Today's day

Because there are only things I can't do There should be a lot of joy in being able to do it. Grow while having fun. By the way, I will update it properly on Saturdays and Sundays.

** 98 days to become a full-fledged engineer **

Recommended Posts

New engineer who will be one serving in 100 days (2nd day)
New engineer who will be one serving in 100 days (day 0)
New engineer who will be one serving in 100 days (5th day)
New engineer who will be one serving in 100 days (3rd day)
New engineer who will be one serving in 100 days (6th day)
New engineer who will be one serving in 100 days (1st day)
New engineer who will be one serving in 100 days (4th day)
26th day of engineer who will become full-fledged in 100 days
28th day of an engineer who will become a full-fledged person in 100 days
Java beginners make poker games in 4 days (2nd day)