Git: Difference between revisions
No edit summary |
|||
| Line 22: | Line 22: | ||
=== Reverting Changes === | === Reverting Changes === | ||
To revert | To revert all changes in the current repository, use: | ||
{{highlight|lang=terminal|code= | |||
## Fetch latest from remote | |||
# git fetch --all | |||
## Reset all changes fetched previously. | |||
# git reset --hard HEAD | |||
}} | |||
To revert a specific file from a specific revision, use {{code|git checkout}}. | |||
{{highlight|lang=terminal|code= | |||
# git checkout <revision> <filename> | |||
}} | |||
=== Remote Origins === | === Remote Origins === | ||
Revision as of 19:42, 19 January 2016
Quick Use Guide
As someone who used SVN for the last decade, switching over to git was slightly confusing since the terminology is different. Hopefully, this usage guide will help.
Committing Files
A commit is like a snapshot and allows you to save the current state of the repository. Unlike in SVN where files are manually included/excluded when a commit is made, git allows files to be staged or unstaged prior to the commit being created. Staged files will always be added to the next commit made.
Typically, you will want to stage all files for commit which can be done by running:
git add -A .
Run git status to see all files that are staged as well as any changed but unstaged files.
git status
To commit all the staged files with a message:
git commit -m 'message'
Reverting Changes
To revert all changes in the current repository, use:
## Fetch latest from remote
# git fetch --all
## Reset all changes fetched previously.
# git reset --hard HEAD
To revert a specific file from a specific revision, use git checkout.
# git checkout <revision> <filename>
Remote Origins
Git allows you to push/pull changes from other remote git repositories. Remote repositories can be in another path or hosted somewhere on the internet.
To see your repository's remotes:
git remote -v
To add a new remote: {{Highlight|lang=bash|code= git remote add origin git@gitlab-blah:user/repo.git }
To remove a remote:
git remote rm origin
If your remote uses SSH, you will most likely need to configure SSH in order to make use of SSH key based authentication. You can read more about this at SSH Configuration File, but the basic idea is to create a SSH configuration file at ~/.ssh/config defining the remote's host.
Host gitlab-remote
User git
HostName git.example.com
IdentityFile ~/.ssh/gitlab-remote
Pushing / Pulling
After making a new change in your repository, you may want to push your changes out to other repositories. Do so by running:
git push
You may also specify a specific remote and branch as well. Eg: git push remote-name branch-name.
Conversely, to retrieve changes from another repository, run
git pull