Scribd
Upload
87 views

Git Commands

This document provides a list of basic Git commands for common tasks like initializing a local repository, tracking and committing changes, branching, merging, and more. It includes the command syntax and a brief explanation for each command, such as using "git init" to initialize a new local repository, "git add" to add files to staging, and "git commit" to commit changes. The goal is to help users get started with basic Git functionality through examples of typical workflows and commands.

Uploaded by

markus_x86
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
87 views

Git Commands

This document provides a list of basic Git commands for common tasks like initializing a local repository, tracking and committing changes, branching, merging, and more. It includes the command syntax and a brief explanation for each command, such as using "git init" to initialize a new local repository, "git add" to add files to staging, and "git commit" to commit changes. The goal is to help users get started with basic Git functionality through examples of typical workflows and commands.

Uploaded by

markus_x86
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Bitbucket Server

Bitbucket Server 4.5

Git resources

Bitbucket Server was previously known as Atlassian Stash. Learn more.

Basic Git commands


Here is a list of some basic Git commands to get you going with Git.
For more detail, check out the Atlassian Git Tutorials for a visual introduction to Git commands and
workflows, including examples.
Git task

Notes

Git commands

Tell Git
who you
are

Configure the
author name and
email address to
be used with your
commits.

git config --global user.name "Sam Smith"

Note that Git

git config--globaluser.email [email protected]

strips some
characters (for
example trailing
periods) from
user.name.
Create a
new local
repository
Check out
a
repository

Add files

Commit

git init

Create a working
copy of a local
repository:

git clone /path/to/repository

For a remote
server, use:

git clone username@host:/path/to/repository

Add one or more


files to staging
(index):

git add <filename>

Commit changes
to head (but not
yet to the remote
repository):

git commit -m "Commit message"

Commit any files


you've added with

git commit -a

git add *

git add, and


also commit any
files you've
changed since
then:
Push

Send changes to
the master branch
of your remote
repository:

git push origin master

Status

List the files


you've changed
and those you still
need to add or
commit:

git status

Connect to
a remote
repository

If you haven't
connected your
local repository to
a remote server,
add the server to
be able to push to
it:

git remote add origin <server>

List all currently


configured remote
repositories:

git remote -v

Branches

Create a new
branch and switch
to it:

git checkout -b <branchname>

Switch from one


branch to another:

git checkout <branchname>

List all the


branches in your
repo, and also tell
you what branch
you're currently in:

git branch

Delete the feature


branch:

git branch -d <branchname>

Push the branch


to your remote
repository, so
others can use it:

git push origin <branchname>

Push all branches


to your remote
repository:

git push --all origin

Delete a branch
on your remote
repository:

git push origin :<branchname>

Update
from the
remote
repository

Fetch and merge


changes on the
remote server to
your working
directory:

git pull

To merge a
different branch
into your active
branch:

git merge <branchname>

View all the


merge conflicts:

git diff

View the conflicts


against the base
file:

git diff --base <filename>


git diff <sourcebranch> <targetbranch>

Preview changes,
before merging:

Tags

After you have


manually resolved
any conflicts, you
mark the changed
file:

git add <filename>

You can use

git tag 1.0.0 <commitID>

tagging to mark a
significant
changeset, such
as a release:

Undo local
changes

CommitId is the
leading
characters of the
changeset ID, up
to 10, but must be
unique. Get the ID
using:

git log

Push all tags to


remote repository:

git push --tags origin

If you mess up,


you can replace
the changes in
your working tree
with the last
content in head:

git checkout -- <filename>

Changes already
added to the
index, as well as
new files, will be
kept.

Search

Instead, to drop
all your local
changes and
commits, fetch the
latest history from
the server and
point your local
master branch at
it, do this:

git fetch origin

Search the
working directory
for foo():

git grep "foo()"

Was this helpful?

Yes

No

git reset --hard origin/master

You might also like