anchor.diff:      }
   }
   ----
  -
   This options ensures that `4.0.51.Final` will be used only for `gatling` configurations, leaving other dependencies unchanged.
   
  +== Release a new version
  +
  +. NodeJS and Npm must be installed.
  +. Create `GitHub` https://github.com/settings/tokens/new[access token]. Only `repo` scope is required.
  +. Install https://github.com/release-it/release-it[release-it]
  ++
  +  $ npm install -g release-it @release-it/conventional-changelog
  +
  +. Run
  ++
  +[source, bash]
  +----
  +$ env GITHUB_TOKEN=${....} release-it --ci patch <1> <2>
  +----
  +<1> paste token value from step *2*
  +<2> can be `patch`, `minor`, `major`
  +
  +. Release script will create and push tag to `GitHub`, create a release with a changelog in `GitHub` and publish plugin to `Gradle` plugin portal.
  +
  
positive.code: }
  ----
  
  Filtering simulations::
  +
  [source,groovy]
  ----
  gatling {
  
negative.code: 
  == Gatling configuration
  
  === Override gatling.conf settings
  
  To override https://github.com/gatling/gatling/blob/master/gatling-core/src/main/resources/gatling-defaults.conf[default parameters] of `Gatling`
  just put own version of `gatling.conf` into `src/gatling/resources`.
  
  === Logging management
  
  `Gatling` uses http://logback.qos.ch/documentation.html[Logback] to customize its output.
  To change logging behaviour, put your `logback.xml` into resources folder,
  `src/gatling/resources`.
  
  If no custom `logback.xml` provided,
  by default plugin will implicitly use following configuration.
  
  .Default `logback.xml` created by the plugin
  [source,xml]
  ----
  <?xml version="1.0" encoding="UTF-8"?>
  