- Created by Paul Watson [Atlassian], last modified on Nov 25, 2014
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. Note that Git strips some characters (for example trailing periods) from |
|
| ||
Create a working copy of a local repository: | | |
For a remote server, use: | | |
Add one or more files to staging (index): | | |
Commit changes to head (but not yet to the remote repository): | | |
Commit any files you've added with git add , and also commit any files you've changed since then: | | |
Send changes to the master branch of your remote repository: | | |
Status | List the files you've changed and those you still need to add or commit: | |
If you haven't connected your local repository to a remote server, add the server to be able to push to it: | | |
List all currently configured remote repositories: | git remote -v | |
Create a new branch and switch to it: | | |
Switch from one branch to another: | | |
List all the branches in your repo, and also tell you what branch you're currently in: | | |
Delete the feature branch: | | |
Push the branch to your remote repository, so others can use it: | | |
Push all branches to your remote repository: | | |
Delete a branch on your remote repository: | | |
Update from the remote repository
| Fetch and merge changes on the remote server to your working directory: | |
To merge a different branch into your active branch: | | |
View all the merge conflicts: View the conflicts against the base file: Preview changes, before merging: |
| |
After you have manually resolved any conflicts, you mark the changed file: | | |
Tags | You can use tagging to mark a significant changeset, such as a release: | |
CommitId is the leading characters of the changeset ID, up to 10, but must be unique. Get the ID using: | | |
Push all tags to remote repository: | | |
If you mess up, you can replace the changes in your working tree with the last content in head: Changes already added to the index, as well as new files, will be kept. | | |
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: | | |
Search | Search the working directory for foo() : | git grep "foo()" |
LF auto C |
| git config --global core.autocrlf true |