Learning GitHub for Source Management (Part 2)

Today I am learning to use git to push any changes I have made to my project locally to the online repository for the project. I have already made my repository online and created the project along with the initial COMMIT.

One thing that developers MUST keep in mind is that there may be changes made to code on the server by other developers on the team that we do not currently have.

So, even if you are 100% certain no one has made changes, it is best practice to get into the habit of doing a PULL-COMMIT-PUSH.

PULL — merges any changes on the server with the changes you have made locally.

COMMIT — gets your changes ready to send to the server (but does not actually make that commitment .

PUSH — sends the changes you have committed to the server to make a new ‘branch’ or version of all the changes you added.

I have made a few changes to the Version-Control project. When I request the status of the project, it will show me anything that has changed. For example, here I have added a simple cube and the script to rotate it constantly along the Z-axis. Next I added the changes to the list to commit and then pushed it to the server side repository.

The status command will show any changes that have not been committed.

And now your changes, along with the description you added are in the master branch on GitHub. 😊

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Michael Hatfield

Michael Hatfield

Math and science teacher / self-taught programmer and Unity game developer working hard to get into the game development industry fulltime.