anchor.diff:  [NOTE]
   ====
   {product-title} will not automatically add a source secret to a build
  -configuration which already contains a source secret.
  +configuration that already contains a source secret.
   ====
   
   If multiple source secrets match the URI of a particular source repository,
  -{product-title} will select a secret with a longest match.  This allows for
  +{product-title} will select the secret with the longest match. This allows for
   basic overriding, as in the following example.
   
   The following fragment shows two partial source secrets, the first matching any
  -server in the domain `mycorp.com` accessed by HTTPS; the second overriding
  +server in the domain `mycorp.com` accessed by HTTPS, and the second overriding
   access to servers mydev1.mycorp.com and mydev2.mycorp.com:
   
   ====
  
positive.code: that it would not normally have access to, such as private repositories or
  repositories with self-signed or untrusted SSL certificates.
  
  The following source secret configurations are supported.  Follow the link to
  learn how to create a source secret of the given configuration.
  
  - xref:gitconfig-file[Gitconfig File]
  - xref:basic-authentication[Basic Authentication]
  - xref:ssh-key-authentication[SSH Key Authentication]
  - xref:trusted-certificate-authorities[Trusted Certificate Authorities]
  
negative.code: ====
  
  Builds are run with the *builder* service account, which must have access to any
  source secrets used. Access is granted with the following command:
  
  ----
  $ oc secrets link builder mysecret
  ----
  
  [[automatic-addition-of-a-source-secret-to-a-build-configuration]]
  ===== Automatic Addition of a Source Secret to a Build Configuration
  
  {product-title} can automatically add a source secret to relevant build
  configurations if the source secret includes one or more annotations prefixed
  with `build.openshift.io/source-secret-match-uri-`. The value of each annotation
  indicates a URI pattern of a source repository against which the secret matches.
  The URI pattern must consist of:
  
  - a valid scheme (`*://`, `git://`, `http://`, `https://` or `ssh://`).
  - a host (`\*` or a valid hostname or IP address optionally preceded by `*.`).
  - a path (`/\*` or `/` followed by any characters optionally including `*` characters).
  
  In all of the above, a `*` character is interpreted as a wildcard.
  