anchor.diff:  
   Name::
   
  -  Git uses a `shortname` to simplify user references to the URL of the remote repository.
  -  The default `shortname` is `origin`.
  +  Git uses a shortname to simplify user references to the URL of the remote repository.
  +  The default shortname is `origin`.
     Other values may be assigned and then used throughout the job definition to refer to the remote repository.
   
   Refspec::
   
  -  A `refspec` maps remote branches to local references.
  -  It defines the branches ags which will be fetched from the remote repository into the agent workspace.
  -  The `refspec` can be used with the <<honor-refspec-on-initial-clone,honor refspec on initial clone>> option in the <<advanced-clone-behaviours,advanced clone behaviors>> to limit the number of remote branches mapped to local references.
  -  Refer to the link:https://git-scm.com/book/en/v2/Git-Internals-The-Refspec[git refspec documention] for more refspec details.
  +  A refspec maps remote branches to local references.
  +  It defines the branches and tags which will be fetched from the remote repository into the agent workspace.
  ++
  +A refspec defines the remote references that will be retrieved and how they map to local references.
  +If left blank, it will default to the normal `git fetch` behavior and will retrieve all branches.
  +This default behaviour is sufficient for most cases.
  ++
  +The default refspec is `+refs/heads/*:refs/remotes/REPOSITORYNAME/` where REPOSITORYNAME is the value you specify in the above repository "Name" field.
  +The default refspec retrieves all branches.
  +If a checkout only needs one branch, then a more restrictive refspec can reduce the data transfer from the remote repository to the agent workspace.
  +For example, `+refs/heads/master:refs/remotes/origin/master` will retrieve only the master branch and nothing else.
  ++
  +The refspec can be used with the <<honor-refspec-on-initial-clone,honor refspec on initial clone>> option in the <<advanced-clone-behaviours,advanced clone behaviors>> to limit the number of remote branches mapped to local references.
  +If "honor refspec on initial clone" is not enabled, then a default refspec for its initial fetch.
  +This maintains compatibility with previous behavior and allows the job definition to decide if the refspec should be honored on initial clone.
  ++
  +Multiple refspecs can be entered by separating them with a space character.
  +The refspec value `+refs/heads/master:refs/remotes/origin/master +refs/heads/develop:refs/remotes/origin/develop` retrieves the master branch and the develop branch and nothing else.
  ++
  +Refer to the link:https://git-scm.com/book/en/v2/Git-Internals-The-Refspec[git refspec documention] for more refspec details.
   
   [[using-credentials]]
   === Using Credentials
  
positive.code: These options allow you to perform a merge to a particular branch before building.
  For example, you could specify an integration branch to be built, and to merge to master.
  In this scenario, on every change of integration, Jenkins will perform a merge with the master branch, and try to perform a build if the merge is successful.
  It then may push the merge back to the remote repository if the Git Push post-build action is selected.
  
  Name of repository::
  
  
negative.code: --
  
  The git plugin provides fundamental git operations for Jenkins projects.
  It can poll, fetch, checkout, branch, list, merge, tag, and push repositories.
  
  toc::[]
  
  