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: ----
  ====
  
  Add a `build.openshift.io/source-secret-match-uri-` annotation to a pre-existing
  secret using:
  
  ----
  $ oc annotate secret mysecret 'build.openshift.io/source-secret-match-uri-1=https://*.mycorp.com/*'
  ----
  
  [[manual-addition-of-a-source-secret-to-a-build-configuration]]
  ===== Manual Addition of a Source Secret to a Build Configuration
  
  Source secrets can be added manually to a build configuration by adding a
  `sourceSecret` field to the `source` section inside the `BuildConfig` and
  