Git Command and Meaning

 1.)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"
git config --global user.email sam@example.com

2.)Create a new local repository-->
git init

3.)Check out a repository-->
A.)Create a working copy of a local repository:

git clone /path/to/repository

B.)For a remote server, use:

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

4.)Check Status
List the files you've changed and those you still need to add or commit:

git status

5.)Add one or more files to staging (index):
git add <filename>

git add *

6.)Commit The changes:
A.)Commit changes to head (but not yet to the remote repository):

git commit -m "Commit message"

B.)Commit any files you've added with git add, and also commit any files you've changed since then:

git commit -a

7.)Push The Changes.

Send changes to the master branch of your remote repository:

git push origin master

8.)Connect to a remote repository.

A.)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>

B.)List all currently configured remote repositories:

git remote -v

9.)Branches.

A.)Create a new branch and switch to it:

git checkout -b <branchname>
B.)Switch from one branch to another:

git checkout <branchname>
C.)List all the branches in your repo, and also tell you what branch you're currently in:

git branch
D.)Delete the feature branch:

git branch -d <branchname>

F.)Push the branch to your remote repository, so others can use it:

git push origin <branchname>
G.)Push all branches to your remote repository:

git push --all origin
H.)Delete a branch on your remote repository:

git push origin :<branchname>

10.)Update from the remote repository

A.)Fetch and merge changes on the remote server to your working directory:

git pull

B.)To merge a different branch into your active branch:

git merge <branchname>

C.)View all the merge conflicts:
   View the conflicts against the base file:
       Preview changes, before merging:

        git diff
git diff --base <filename>
        git diff <sourcebranch> <targetbranch>

    D.)After you have manually resolved any conflicts, you mark the changed file:

     git add <filename>

11.)Tags
A.)You can use tagging to mark a significant changeset, such as a release:

     git tag 1.0.0 <commitID>

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

     git log

    C.)Push all tags to remote repository:

     git push --tags origin

12.)Undo local changes.

A.)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.

git checkout -- <filename>

B.)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

git reset --hard origin/master

13.)Search
Search the working directory for smart():

git grep "smart()"


Some specific scenario.

git fetch origin
git reset --hard origin/master
git pull
You should be able to force your local revision to the remote repo by using 
git push -f <remote> <branch>
(e.g. git push -f origin master). Leaving off <remote> and <branch> will force push all local branches that have set --set-upstream.

3.)Fatal: I don't handle protocol 'https'

-->Please Check the URL , you are using.

Comments

Popular posts from this blog

API Automation using Rest Assured

Security Testing

Manage Jenkins