#GIT COMMANDS HOW TO#

This command returns the current state of the repository. My first commit messageġ file changed, 0 insertions(+), 0 deletions(-)Ĭreate mode 100644 homepage/index.html git status

In Practice: $ git commit -m 'My first commit message' $ git commit -m 'Commit message in quotes' Adding a commit message helps to find a particular change or understanding the changes. It’s best practice to include a message with each commit explaining the changes made in a commit. For easy reference, each commit has a unique ID. Record the changes made to the files to a local repository. In Practice: # To add all files not staged: There are a few different ways to use git add, by adding entire directories, specific files, or all unstaged files. Before a file is available to commit to a repository, the file needs to be added to the Git index (staging area). Initialized empty Git repository in /Users/computer-name/Documents/website/.git/ git addĪdds files in the to the staging area for Git. $ cd /Users/computer-name/Documents/website

In Practice: # change directory to codebase After running git init, adding and committing files/directories is possible. This is the first step in creating a repository. This command turns a directory into an empty Git repository. If you’re getting started with Git also check out our fantastic guide on the topic. Knowing what actions the client is performing in the background is beneficial to understanding how Git works. Git has many great clients that allow you to use Git without the command line. Our hope is that this makes Git easier to use on a daily basis.

#GIT COMMANDS HOW TO#

To help with that, we’ve put together a list of common Git commands, what each one means, and how to use them. Working with Git on the command line can be daunting.