Using Git to Create Products

This is a beginner's guide to using Git to make a product. Welcome!

To submit product updates you must have Git installed and know the basics of interacting with Git. Don't worry - it's easy to get started!

Download and Installation

If you haven't already downloaded and installed Git, read this guide for more information:

Beginner's Guide to Git

If you are new to Git, it is highly recommended that you install a graphical user interface, instead of using the command line.

The guide will assume that you are using the command line, but is still worth reading to understand the concepts. If you use a graphical program to interact with Git, you will want to follow any guide that program offers its users.

Cloning Your Product

First you will clone the product you created. You can find the Git URL on your product page.

git tab

Copy the URL in that tab, and clone the product. The clone command downloads the Git repository for you so you can make changes.

git clone

Making Your First Commit

A commit is a change that you tell Git you'd like to make. Until you use the commit command, Git will not pick up on any changes to your project.

First create a file - any file - in the project directory. Before we tell Git to commit the changes, we have to tell Git the file exists by using git add. Do the following command:

git add .

Git has now added every file that is in the current directory to its index. Now we can tell Git we are preparing to send our update by committing the changes.

git commit -m "my first change"

The -m flag here tells Git we would like to also add a message. This is useful for telling customers what changed in the commit.

Pushing Changes

So far we created a file, told Git it existed with add, and then told Git we are ready to submit those changes for everyone to see with commit. The only thing left is to send the changes with push.

git push origin master

The push command tells Git we want to publish all of our changes and send them to The origin and master keywords tell Git which code base we want to push. This concept isn't important right now. At this point you should get a success message that the changes were accepted.

A Deeper Git Introduction

If you are caught up on the concepts stated, you might want to checkout out a Git graphical user interface. Instead of using a command line you will use a visual program to make changes.

If you like the command line but want to learn more, the official Git docs are pretty great.

Links to both more Git documentation and graphical user interfaces can be found in the following Git introduction guide:

Beginner's Guide to Git