The Bitbucket command-line gives us multiple functionalities, and it’s very powerful if we’re comfortable with the Linux shell. Here you can see some basic commands to use the tool:
Configure the author name and email address to be used with your commits. |
git config --global user.name "Sam Smith"
|
Create a new local repository | git init |
Create a working copy of a local repository | git clone /path/to/repository |
Create a working copy of a local repository for a remote server |
git clone username@host:/path/to/repository |
Add one or more files | git add <filename> git add * |
Commit changes to head | git commit -m "Commit message" |
Commit any files you've added(git add), and also commit any files you've changed since then | git commit -a |
Send changes to the master branch of your remote repository | git push origin master |
List the files you've changed and those you still need to add or commit | git status |
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 |
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> |
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> |
Preview changes, before merging |
git diff <sourcebranch> <targetbranch> |
After you have manually resolved any conflicts, you mark the changed file |
git add <filename> |
You can use tagging to mark a significant changeset, such as a release |
git tag 1.0.0 <commitID> git log |
Push all tags to remote repository | git push --tags origin |
Undo local changes | git checkout -- <filename> git fetch origin git reset --hard origin/master |
Search the working directory | git grep " " |