anchor.diff:  be set there. Just provide a mapping for the `gradle-props-substition` looking like this `foo=spring-cloud-contract` and the result
   (e.g for sc-contract version `2.0.0.RELEASE`) will be an updated `gradle.properties` with entry `foo=2.0.0.RELEASE`
   - `releaser.pom.branch` - Which branch of Spring Cloud Release should be checked out. Defaults to "master",
  -- `releaser.pom.ignored-pom-regex` - List of regular expressions of ignored poms. Defaults to test projects and samples.,
  +- `releaser.pom.ignored-pom-regex` - List of regular expressions of ignored poms. Defaults to test projects and samples.
  +The defaults are `"--releaser.pom.ignored-pom-regex="^.*\\.git/.*$,^.*spring-cloud-contract-maven-plugin/src/test/projects/.*$,^.*spring-cloud-contract-maven-plugin/target/.*$,^.*samples/standalone/[a-z]+/.*$"`
   - `releaser.working-dir` - By default Releaser assumes running the program from the current working directory.
   
   TIP: You can pass the options either via system properties or via application arguments.
  
positive.code: $ ./mvnw clean install
  ----
  
  === How to run it (interactive mode)
  
  Go to your project (e.g. Spring Cloud Sleuth)
  
negative.code: $ java -jar ~/repo/spring-cloud-release-tools/spring-cloud-release-tools-spring/target/spring-cloud-release-tools-spring-1.0.0.BUILD-SNAPSHOT.jar --releaser.pom.branch=vDalston.SR1 --spring.config.name=releaser
  ----
  
  The application will start running from your working directory. Running this code
  follows the convention that you have the OAuth token environment variable set. It also assumes
  that you might have some custom configuration in `config/releaser.yml` file. This setting is optional - if
  you don't have that file, nothing will happen.
  
  TIP:  It is important that you clone the repository you are going to release using SSH in order for the
  `releaser` to be able to push tags and commit changes automatically.
  