4.3 KiB
| stage | group | info |
|---|---|---|
| Create | Source Code | To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments |
Common Git commands
Learn more about the most commonly used Git commands.
git add
Use git add to files to the staging area.
git add <file_path>
You can recursively stage changes from the current working directory with git add ., or stage all changes in the Git repository with git add --all.
git blame
Use git blame to report which users changed which parts of a file.
git blame <file_name>
You can use git blame -L <line_start>, <line_end> to check a
specific range of lines.
For example, to check which user most recently modified line five of
example.txt:
$ git blame -L 5, 5 example.txt
123abc (Zhang Wei 2021-07-04 12:23:04 +0000 5)
git bisect
Use git bisectto use binary search to find the commit that introduced a bug.
Start by identifying a commit that is "bad" (contains the bug) and a commit that is "good" (doesn't contain the bug).
git bisect start
git bisect bad # Current version is bad
git bisect good v2.6.13-rc2 # v2.6.13-rc2 is known to be good
git bisectthen picks a commit in between the two points and asks you identify if the commit is "good" or "bad" with git bisect goodor git bisect bad. Repeat the process until the commit is found.
git checkout
Use git checkout to switch to a specific branch.
git checkout <branch_name>
To create a new branch and switch to it, use git checkout -b <branch_name>.
git clone
Use git clone to copy an existing Git repository.
git clone <repository>
git commit
Use git commit to commits staged changes to the repository.
git commit -m "<commit_message>"
If the commit message contains a blank line, the first line becomes the commit subject while the remainder becomes the commit body. Use the subject to briefly summarize a change, and the commit body to provide additional details.
Use git commit --amend to modify the most recent commit.
git commit --amend
git init
Use git init to initialize a directory so Git tracks it as a repository.
git init
A .git file with configuration and log files is added to the
directory. You shouldn't edit the .git file directly.
The default branch is set to master. You can change the name of the
default branch with git branch -m <branch_name>, or initialize with
git init -b <branch_name>.
git pull
Use git pull to get all the changes made by users since the last
time you cloned or pulled the project.
git pull <optional_remote> <branch_name>
git push
Use git push to update remote refs.
git push
git reflog
To display a list of changes to the Git reference logs, use git reflog.
git reflog
By default, git reflog shows a list of changes to HEAD.
git remote add
Use git remote add to tell Git which remote repository in GitLab is
linked to a local directory.
git remote add <remote_name> <repository_url>
When you clone a repository, by default the source repository is
associated with the remote name origin.
git log
To display a list of commits in chronological order, use git log.
git log
git show
To show information about an object in Git, use git show.
For example, to see what commit HEAD points to:
$ git show HEAD
commit ab123c (HEAD -> main, origin/main, origin/HEAD)
git merge
To combine the changes from one branch with another, use git merge.
For example, to apply the changes in feature_branch to the target_branch:
git checkout target_branch
git merge feature_branch
git rebase
To rewrite the commit history of a branch, use git rebase.
You can use git rebase to resolve merge conflicts.
git rebase <branch_name>
In most cases, you want to rebase against the default branch.
git reset
To undo a commit, use git reset to rewind the commit history and continue on from an earlier commit.
git reset
git status
Use git status to show the status of working directory and staged files.
git status