anchor.diff:  // Do not edit this file (e.g. go instead to src/main/asciidoc)
   
   image::https://badges.gitter.im/Join%20Chat.svg[Gitter, link="https://gitter.im/spring-cloud/spring-cloud-contract?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge"]
  -image::https://codecov.io/gh/spring-cloud/spring-cloud-contract/branch/1.0.x/graph/badge.svg["codecov", link="https://codecov.io/gh/spring-cloud/spring-cloud-contract"]
  +image::https://codecov.io/gh/spring-cloud/spring-cloud-contract/branch/master/graph/badge.svg["codecov", link="https://codecov.io/gh/spring-cloud/spring-cloud-contract"]
   image::https://circleci.com/gh/spring-cloud/spring-cloud-contract.svg?style=svg["CircleCI", link="https://circleci.com/gh/spring-cloud/spring-cloud-contract"]
   
   == Spring Cloud Contract
  
positive.code: 
  === Sign the Contributor License Agreement
  Before we accept a non-trivial patch or pull request we will need you to sign the
  https://support.springsource.com/spring_committer_signup[contributor's agreement].
  Signing the contributor's agreement does not grant anyone commit rights to the main
  repository, but it does mean that we can accept your contributions, and you will get an
  author credit if we do.  Active contributors might be asked to join the core team, and
  given the ability to merge pull requests.
  
  === Code Conventions and Housekeeping
  None of these is essential for a pull request, but they will all help.  They can also be
  added after the original pull request but before a merge.
  
negative.code: * Use the Spring Framework code format conventions. If you use Eclipse
    you can import formatter settings using the
    `eclipse-code-formatter.xml` file from the
    https://raw.githubusercontent.com/spring-cloud/spring-cloud-build/master/spring-cloud-dependencies-parent/eclipse-code-formatter.xml[Spring
    Cloud Build] project. If using IntelliJ, you can use the
    http://plugins.jetbrains.com/plugin/6546[Eclipse Code Formatter
    Plugin] to import the same file.
  