chutney 3.14.0 → 3.15.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3c21346027cfc0954890e1e287dbf282e76567e58267f9da730d2132d0ae83e1
-  data.tar.gz: d0a823dcd25b1bccc00bc873444f079e1be6421aad287c624a26fd3b6e11dac2
+  metadata.gz: e73618c6f81cbfab1e5928582ac4123976b85f8e81e325258a53842e60c8b3a0
+  data.tar.gz: 8cafe000236c2508a6aabf52c29abcba07cc073305e4a65773c61bea660025aa
 SHA512:
-  metadata.gz: 77880b9602738619b732d6eeee96a05cab06177c159fce4b0a150af9684d166e65314408548edaf42cc735cb93eef88164338ec32561210c19a9cabe3a22ab38
-  data.tar.gz: 3e650442d104bd17c8cdffbc5956291e9cb288a4b0fbca34cbdb0dc6c6b7413e8ed40bff9d4272e48aebc6062bb459c89f627f08fa29660fbc1e279f967bf5dd
+  metadata.gz: 246eee2cb29c53d2542cb8791be4c8720ae5847d1633b8b5500ed68fc80ce4e3109638055f547c6693aebf6f25c2da232d704fbcfa1007da1b9a64b2d5388bc8
+  data.tar.gz: 32c89a884eae22053fd85dbdcb74f8500a0cf2d7a1a62d6a801d69af6a5fae6e8068eeee0370bfa482e363a2a968beb9e6bfcdfd88207f660a9d4cc20151df94

data/config/chutney_defaults.yml

@@ -2,10 +2,10 @@ AvoidColonsAtStartOfNames:
   Enabled: true
 AvoidCommaInTags:
   Enabled: true
-AvoidOutlineForSingleExample:
-  Enabled: true
 AvoidFullStop:
   Enabled: true
+AvoidOutlineForSingleExample:
+  Enabled: true
 AvoidScripting:
   Enabled: true
 AvoidSplatStepsInBackground:

data/lib/chutney/linter/avoid_mutually_exclusive_tags.rb

@@ -0,0 +1,56 @@
+# frozen_string_literal: true
+
+module Chutney
+  # service class to lint for avoiding mutually exclusive tags
+  class AvoidMutuallyExclusiveTags < Linter
+    def lint
+      return if feature.nil?
+
+      feature_tags = tags_for(feature)
+      scenarios do |_feature, scenario|
+        scenario_tags = tags_for(scenario)
+        # use [nil] for plain scenarios so the loop runs once with no example tags
+        examples_blocks = scenario.respond_to?(:examples) ? scenario.examples : [nil]
+
+        tag_groups.each do |group|
+          check_group(group, feature_tags, scenario, scenario_tags, examples_blocks)
+        end
+      end
+    end
+
+    private
+
+    def check_group(group, feature_tags, scenario, scenario_tags, examples_blocks)
+      # seed seen_tags with any exclusive tags already present at feature/scenario level
+      seen_tags = (feature_tags + scenario_tags) & group
+      reported_scenario = (scenario_tags & group).any? ? scenario : nil
+      reported_examples = nil
+
+      # accumulate exclusive tags across each "Examples:" block, tracking the last element with a group tag
+      examples_blocks.each do |examples|
+        example_tags = examples ? tags_for(examples) : []
+        seen_tags += example_tags & group
+        if example_tags.intersect?(group)
+          reported_examples = examples
+          reported_scenario = scenario
+        end
+      end
+
+      return if seen_tags.length < 2
+
+      # report at the deepest location: examples > scenario > feature
+      formatted = seen_tags.map { |t| "@#{t}" }.join(', ')
+      add_issue(
+        I18n.t('linters.avoid_mutually_exclusive_tags', tags: formatted),
+        feature,
+        reported_scenario,
+        reported_examples
+      )
+    end
+
+    def tag_groups
+      groups = configuration['TagGroups'] || []
+      groups.is_a?(Array) ? groups : []
+    end
+  end
+end

data/lib/chutney/linter/avoid_tags.rb

@@ -6,31 +6,31 @@ module Chutney
     def lint
       return if feature.nil?
 
-      feature_tags = tags_for(feature)
-      feature_tags_to_avoid_found = feature_tags & tags_to_avoid
-
-      unless feature_tags_to_avoid_found.empty?
-        feature_tags_to_avoid_found = feature_tags_to_avoid_found.map { |tag| tag.prepend('@') }
-        add_issue(I18n.t('linters.avoid_tags', tags: feature_tags_to_avoid_found.join(', ')), feature)
-      end
+      check_tags(feature, feature)
 
       scenarios do |_feature, scenario|
-        scenario_tags = tags_for(scenario)
-        scenario_tags_to_avoid_found = scenario_tags & tags_to_avoid
+        check_tags(scenario, feature, scenario)
 
-        unless scenario_tags_to_avoid_found.empty?
-          scenario_tags_to_avoid_found = scenario_tags_to_avoid_found.map { |tag| tag.prepend('@') }
-          add_issue(I18n.t('linters.avoid_tags', tags: scenario_tags_to_avoid_found.join(', ')), feature, scenario)
+        next unless scenario.respond_to?(:examples)
+
+        scenario.examples.each do |examples|
+          check_tags(examples, feature, scenario, examples)
         end
       end
     end
 
-    def tags_to_avoid
-      tags_to_avoid = configuration['Tags'] || []
+    private
 
-      return [] unless tags_to_avoid.is_a?(Array)
+    def check_tags(element, *location)
+      found = tags_for(element) & tags_to_avoid
+      return if found.empty?
 
-      tags_to_avoid
+      add_issue(I18n.t('linters.avoid_tags', tags: found.map { |t| "@#{t}" }.join(', ')), *location)
+    end
+
+    def tags_to_avoid
+      tags = configuration['Tags'] || []
+      tags.is_a?(Array) ? tags : []
     end
   end
 end

data/lib/chutney/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Chutney
-  VERSION = '3.14.0'
+  VERSION = '3.15.0'
 end

data/lib/chutney.rb

@@ -7,6 +7,7 @@ require 'chutney/linter'
 require 'chutney/linter/avoid_colons_at_start_of_names'
 require 'chutney/linter/avoid_comma_in_tags'
 require 'chutney/linter/avoid_full_stop'
+require 'chutney/linter/avoid_mutually_exclusive_tags'
 require 'chutney/linter/avoid_outline_for_single_example'
 require 'chutney/linter/avoid_scripting'
 require 'chutney/linter/avoid_splat_steps_in_background'

data/lib/config/locales/en.yml

@@ -9,6 +9,8 @@ en:
       Avoid using commas in tags. Tags should be separated by spaces.
     avoid_full_stop: >- # https://en.wikipedia.org/wiki/Full_stop
       Avoid using a full-stop in steps so that it is easier to re-use them.
+    avoid_mutually_exclusive_tags: >-
+      The following mutually exclusive tags are not allowed to be used together: %{tags}
     avoid_outline_for_single_example: >-
       Avoid using Scenario Outlines when you only have a single example.
       Use a Scenario instead.
@@ -20,7 +22,7 @@ en:
     avoid_splat_steps_in_scenarios: >-
       The Scenario contains a splat step. It should only contain named steps.
     avoid_tags: >-
-      The following tags are not allowed: %{tags}.
+      The following tags are not allowed: %{tags}
     avoid_typographers_quotes: >-
       You are using typographers quotation marks (curly quotes).
       Make sure you intend to use this character and not a neutral quote

data/usechutney.com.site/site/src/docs/rules/avoid-mutually-exclusive-tags.page.md

@@ -0,0 +1,69 @@
+# Avoid Mutually Exclusive Tags
+
+Some tags are mutually exclusive by nature — they represent states or configurations that cannot coexist. For example, `@mobile` and `@desktop`, or `@en` and `@fr`.
+
+AvoidMutuallyExclusiveTags warns you when tags from the same mutually exclusive group appear together across a feature, scenario, or examples block.
+
+## Configuration
+
+```yaml
+AvoidMutuallyExclusiveTags:
+  Enabled: true
+  TagGroups:
+    - - mobile
+      - desktop
+    - - en
+      - fr
+      - de
+```
+
+Each entry in `TagGroups` is a list of tags that are mutually exclusive with each other. Any two or more tags from the same group appearing together will raise an issue.
+
+## Bad
+
+```gherkin
+@mobile @desktop
+Scenario: View the homepage
+  Given I have visited the website
+  When I view the homepage
+  Then I see the welcome message
+```
+
+```gherkin
+@mobile
+Feature: View the homepage
+  @desktop
+  Scenario: See the welcome message
+    Given I have visited the website
+    When I view the homepage
+    Then I see the welcome message
+```
+
+```gherkin
+@mobile
+Feature: View the homepage
+  Scenario Outline: See the welcome message in <language>
+    Given I have visited the website
+    When I view the homepage
+    Then I see the welcome message in <language>
+    @desktop
+    Examples:
+      | language |
+      | English  |
+```
+
+## Good
+
+```gherkin
+@mobile
+Scenario: View the homepage on mobile
+  Given I have visited the website
+  When I view the homepage
+  Then I see the welcome message
+
+@desktop
+Scenario: View the homepage on desktop
+  Given I have visited the website
+  When I view the homepage
+  Then I see the welcome message
+```

data/usechutney.com.site/site/src/docs/rules/{avoid-tags.md → avoid-tags.page.md}

@@ -1,6 +1,7 @@
 # Avoid Tags
 
 Sometimes you just need a tag for you... maybe to filter your scenarios for focused testing?... or maybe you've got some fancy after hook to help with debugging? 
+
 Whatever the reason, you probably didn't mean to commit that to source. 
 
 AvoidTags helps prevent the accidental commit of tags by warning you if you have any tags in your feature file which match a configurable list of tags to avoid.

data/usechutney.com.site/site/src/docs/rules/index.page.md

@@ -7,6 +7,7 @@
 * [Avoid Scripting](/docs/rules/avoid-scripting)
 * [Avoid Splat Steps in Background](/docs/rules/avoid-splat-steps-in-background)
 * [Avoid Splat Steps in Scenarios](/docs/rules/avoid-splat-steps-in-scenarios)
+* [Avoid Tags](/docs/rules/avoid-tags)
 * [Avoid Typographers' Quotes](/docs/rules/avoid-typographers-quotes)
 * [Background Does More Than Setup](/docs/rules/background-does-more-than-setup)
 * [Background Requires Multiple Scenarios](/docs/rules/background-requires-multiple-scenarios)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: chutney
 version: !ruby/object:Gem::Version
-  version: 3.14.0
+  version: 3.15.0
 platform: ruby
 authors:
 - Nigel Brookes-Thomas
@@ -10,7 +10,7 @@ authors:
 - John Gluck
 bindir: exe
 cert_chain: []
-date: 2026-06-11 00:00:00.000000000 Z
+date: 2026-07-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: amatch
@@ -149,17 +149,6 @@ files:
 - chutney.gemspec
 - config/chutney_defaults.yml
 - config/cucumber.yml
-- docs/.keep
-- docs/_config.yml
-- docs/credits.md
-- docs/index.md
-- docs/installation.md
-- docs/logo.png
-- docs/usage/configuration.md
-- docs/usage/index.md
-- docs/usage/output.md
-- docs/usage/rules.md
-- docs/usage/selective_enablement.md
 - examples/emoji.feature
 - exe/chutney
 - exe/chutney-lsp
@@ -179,6 +168,7 @@ files:
 - lib/chutney/linter/avoid_colons_at_start_of_names.rb
 - lib/chutney/linter/avoid_comma_in_tags.rb
 - lib/chutney/linter/avoid_full_stop.rb
+- lib/chutney/linter/avoid_mutually_exclusive_tags.rb
 - lib/chutney/linter/avoid_outline_for_single_example.rb
 - lib/chutney/linter/avoid_scripting.rb
 - lib/chutney/linter/avoid_splat_steps_in_background.rb
@@ -248,11 +238,12 @@ files:
 - usechutney.com.site/site/src/docs/rules/avoid-colons-at-start-of-names.page.md
 - usechutney.com.site/site/src/docs/rules/avoid-comma-in-tags.page.md
 - usechutney.com.site/site/src/docs/rules/avoid-full-stops.page.md
+- usechutney.com.site/site/src/docs/rules/avoid-mutually-exclusive-tags.page.md
 - usechutney.com.site/site/src/docs/rules/avoid-outline-for-single-example.page.md
 - usechutney.com.site/site/src/docs/rules/avoid-scripting.page.md
 - usechutney.com.site/site/src/docs/rules/avoid-splat-steps-in-background.page.md
 - usechutney.com.site/site/src/docs/rules/avoid-splat-steps-in-scenarios.page.md
-- usechutney.com.site/site/src/docs/rules/avoid-tags.md
+- usechutney.com.site/site/src/docs/rules/avoid-tags.page.md
 - usechutney.com.site/site/src/docs/rules/avoid-typographers-quotes.page.md
 - usechutney.com.site/site/src/docs/rules/background-does-more-than-setup.page.md
 - usechutney.com.site/site/src/docs/rules/background-requires-multiple-scenarios.page.md

data/docs/_config.yml

@@ -1,8 +0,0 @@
-remote_theme: pmarsceill/just-the-docs
-logo: "https://raw.githubusercontent.com/BillyRuffian/chutney/master/docs/logo.png"
-title: Chutney
-description: A linter for Gherkin
-aux_links:
-  "Chutney on GitHub":
-    - "https://github.com/BillyRuffian/chutney"
-footer_content: "Copyright &copy; 2019-2020 Nigel Brookes-Thomas. Distributed by an <a href=\"https://github.com/BillyRuffian/chutney/blob/master/LICENSE.txt\">MIT license.</a>"

data/docs/credits.md

@@ -1,15 +0,0 @@
----
-layout: default
-title: Credits
-nav_order: 4
----
-
-# Credits
-
-This linter started life as a fork of the abandoned [gherkin_lint](https://github.com/funkwerk/gherkin_lint) and very great deal of credit for the linting rules goes to the original author(s) of that project.
-
-I've dusted it off and brought it up to date with Cucumber 3 and improved the internals.
-
-# Logo
-
-Pickle jar image by [OpenClipart-Vectors](https://pixabay.com/users/OpenClipart-Vectors-30363/?utm_source=link-attribution&utm_medium=referral&utm_campaign=image&utm_content=576536) from [Pixabay](https://pixabay.com/?utm_source=link-attribution&utm_medium=referral&utm_campaign=image&utm_content=576536).

data/docs/index.md

@@ -1,24 +0,0 @@
----
-layout: default
-title: Home
-nav_order: 1
-permalink: /
----
-
-# These docs are deprecated
-## Please visit [usechutney.com](https://www.usechutney.com/) for the latest documentation
-
-# Best practice for Cucumber
-{: .fs-9 }
-
-
-Chutney tastes your Cumber feature files and lets you know if they're tasty or nasty.
-{: .fs-6 .fw-300 }
-
----
-
-You're trying to follow TDD or ATDD principles, you're writing executable specifications in gherkin using Cucumber, you're trying to do *the right thing* but are you doing *the thing right*?
-
-Cucumber itself is an awesome tool which bridges with gap between business language, software development language and the language of testers. With all these folks interested, it's easy to write problematic and hard to maintain features. Chutney tries to help with that by having a common set of quality rules for your feature files.
-
-Chutney is able to lint feature files in any spoken language supported by Cucumber.

data/docs/installation.md

@@ -1,21 +0,0 @@
----
-layout: default
-title: Installing
-nav_order: 2
----
-
-# Installing
-
-Add this line to your application's Gemfile:
-
-```ruby
-gem 'chutney', require: false
-```
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install chutney

data/docs/usage/configuration.md

@@ -1,12 +0,0 @@
----
-layout: default
-title: Configuration
-parent: Usage
-nav_order: 3
----
-
-# Configuration
-
-Chutney looks for a configuration file in the current directory called `config/.chutney.yml`. This configuration mostly switches on individual linters globally, but a few have addition parameters which can be configured (e.g. the maximum characters in a step).
-
-A default configuration can be found [here](https://github.com/BillyRuffian/chutney/blob/master/config/chutney_defaults.yml).

data/docs/usage/index.md

@@ -1,16 +0,0 @@
----
-layout: default
-title: Usage
-nav_order: 3
-has_children: true
----
-
-# Usage
-
-Chutney expects to be able to find your Cucumber `.feature` files. By default, it will look for a folder called `features` in the current directory and will dig through all subfolders to find features.
-
-You can give Chutney a path (using Ruby's globbing rules) or a single file if you want.
-
-```
-chutney '<wild_card_path>' #default is `features/**/*.feature`
-```

data/docs/usage/output.md

@@ -1,26 +0,0 @@
----
-layout: default
-title: Output & Exit Codes
-parent: Usage
-nav_order: 1
----
-
-# Output
-
-Chutney ships with a few formatters, the default being the Rainbow Formatter (it has coloured terminal output). Others included are the Pie Formatter which presents a textual pie chart of all the violations, and a JSON Formatter which, as is sounds, dumps the result as a JSON string.
-
-You can specify one or formatters with the `-f` flag. For instance...
-
-```
-chutney -f RainbowFormatter -f PieFormatter -f JSONFormatter
-```
-
-## Building Your Own Formatters
-
-Chutney expects formatters to be namespaced to the `Chutney` module and respond to `results=(results_hash)` and `format`. There is a parent class `Chutney::Formatter` which provides a few utility methods you might find useful.
-
-Take a look a the JSONFormatter as the most minimal implementation -- it just calls `to_json` on the hash it is given.
-
-## Exit Codes
-
-Using the command line, Chutney returns 0 if no violations are found, 1 if one or more are found.

data/docs/usage/rules.md

@@ -1,90 +0,0 @@
----
-layout: default
-title: Rules
-parent: Usage
-nav_order: 2
----
-
-# Linting Rules
-
-Chutney enforces its rules with the linters. These are:
-
-[AvoidFullStop](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_full_stop.feature): Don't have a full stop (period) at the end of step because it makes step reuse really hard.
-
-[AvoidOutlineForSingleExample](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_outline_for_single_example.feature): If you only have a single example in your example table, use a plain-old scenario instead.
-
-[AvoidScripting](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_scripting.feature): You have a lot of steps, are you sure you're not scripting the scenario when you should be specifying the behaviour of the system?
-
-[AvoidSplatStepsInBackground](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_splat_steps_in_background.feature): The Background contains a splat step. It should only contain named steps.
-
-[AvoidSplatStepsInScenarios](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_splat_steps_in_scenarios.feature): The Scenario contains a splat step. It should only contain named steps.
-
-[AvoidTags](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_tags.feature): The Feature file contains tags to avoid.
-
-[AvoidTypographersQuotes](https://github.com/BillyRuffian/chutney/blob/master/features/avoid_typographers_quotes.feature): Cutting and pasting from Word documents? Is that pasting in curly-quotes instead of neutral ones you would type on a keyboard? Are you sure that's what you want?
-
-[BackgroundDoesMoreThanSetup](https://github.com/BillyRuffian/chutney/blob/master/features/background_does_more_than_setup.feature): Background in feature files should only do setup activity and so they should only contain `Given` steps.
-
-[BackgroundRequiresMultipleScenarios](https://github.com/BillyRuffian/chutney/blob/master/features/background_requires_multiple_scenarios.feature): If you only have one scenario, don't bother having a Background section.
-
-[BadScenarioName](https://github.com/BillyRuffian/chutney/blob/master/features/bad_scenario_name.feature): You should avoid using words like 'test' or 'check' in your scenario names, instead you should define the behaviour of your system.
-
-[EmptyFeatureFile](https://github.com/BillyRuffian/chutney/blob/master/features/empty_feature_file.feature): The feature should have content and should avoid committing empty features to repositories.
-
-[FileNameDiffersFeatureName](https://github.com/BillyRuffian/chutney/blob/master/features/file_name_differs_feature_name.feature): The feature should have a name that follows the file name.
-
-[GivensAfterBackground](https://github.com/BillyRuffian/chutney/blob/master/features/givens_after_background.feature): If you have a Background section and your scenario needs more preconditions then it should start immediately with an `And` step and not another `Given`.
-
-[InconsistentQuoting](https://github.com/BillyRuffian/chutney/blob/master/features/inconsistent_quoting.feature): Use either single quotation marks *or* double quotation marks around parameters but don't use a mix of the two styles.
-
-[InvalidFileName](https://github.com/BillyRuffian/chutney/blob/master/features/invalid_file_name.feature): Make sure your file name is in snake case, not mixed case or with spaces.
-
-[InvalidStepFlow](https://github.com/BillyRuffian/chutney/blob/master/features/invalid_step_flow.feature): Your scenarios should follow Given → When → Then, in that order.
-
-[MissingExampleName](https://github.com/BillyRuffian/chutney/blob/master/features/missing_example_name.feature): If you have more than one example table in your scenario, they should each be given unique names.
-
-[MissingExampleTable](https://github.com/BillyRuffian/chutney/blob/master/features/missing_example_table.feature): You are missing an example table. You should have at least one example table when using Scenario outlines.
-
-[MissingFeatureDescription](https://github.com/BillyRuffian/chutney/blob/master/features/missing_feature_description.feature): Your feature should have a value statement. These are usually in the form 'As a... I want.. So that...'.
-
-[MissingFeatureName](https://github.com/BillyRuffian/chutney/blob/master/features/missing_feature_name.feature): You should give your features a descriptive name.
-
-[MissingScenarioName](https://github.com/BillyRuffian/chutney/blob/master/features/missing_scenario_name.feature): You should name your scenarios and scenario outlines.
-
-[MissingScenarioOutline](https://github.com/BillyRuffian/chutney/blob/master/features/missing_scenario_outline.feature): You should use Scenario Outline instead of Scenario when there is an Examples table to indicate that this scenario will be run multiple times with different data.
-
-[MissingTestAction](https://github.com/BillyRuffian/chutney/blob/master/features/missing_test_action.feature): You don't have an action (a `When` step) in your scenario.
-
-[MissingVerification](https://github.com/BillyRuffian/chutney/blob/master/features/missing_verification.feature): You don't have a verification step (a `Then` step) in your scenario.
-
-[RequiredTagsStartWith](https://github.com/BillyRuffian/chutney/blob/master/features/required_tags_starts_with.feature): Chutney can enforce a configurable naming prefix for your tags.
-
-[SameSecenario](https://github.com/BillyRuffian/chutney/blob/master/features/same_scenario.feature): Makes sure you don't acidentally duplicate the actions of your scenario. *Since v3.11.0*
-
-[SameTagForDifferentCase](https://github.com/BillyRuffian/chutney/blob/master/features/same_tag_different_case.feature): Don't mix the case of tags which have already appeared. Cucumber tags are case sensitive. *Since 3.1.0*
-
-[SameTagForAllScenarios](https://github.com/BillyRuffian/chutney/blob/master/features/same_tag_for_all_scenarios.feature): You have the same tag for all you scenarios; move the tag to the feature level instead.
-
-[ScenarioNamesMatch](https://github.com/BillyRuffian/chutney/blob/master/features/scenario_names_match.feature): Chutney can enforce a naming convention for your scenario names.
-
-[TagUsedMultipleTimes](https://github.com/BillyRuffian/chutney/blob/master/features/tag_used_multiple_times.feature): Chutney can warn if you have used a tag a lot with a feature.
-
-[TooClumsy](https://github.com/BillyRuffian/chutney/blob/master/features/too_clumsy.feature): This is a very long scenario. Consider writing it more concisely.
-
-[TooLongStep](https://github.com/BillyRuffian/chutney/blob/master/features/too_long_step.feature): This is a very long step. Consider writing it more concisely.
-
-[TooManyDifferentTags](https://github.com/BillyRuffian/chutney/blob/master/features/too_many_different_tags.feature): This feature has a lot of different tags.
-
-[TooManySteps](https://github.com/BillyRuffian/chutney/blob/master/features/too_many_steps.feature): This feature has a lot of steps. Consider writing it more concisely.
-
-[TooManyTags](https://github.com/BillyRuffian/chutney/blob/master/features/too_many_tags.feature): There are a lot of tags in this feature.
-
-[UniqueScenarioNames](https://github.com/BillyRuffian/chutney/blob/master/features/unique_scenario_names.feature): You have duplicated a scenario name when they should be unique.
-
-[UnknownVariable](https://github.com/BillyRuffian/chutney/blob/master/features/unknown_variable.feature): You are referencing a variable which doesn't appear to be defined. This is a source of subtle errors.
-
-[UnusedVariable](https://github.com/BillyRuffian/chutney/blob/master/features/unused_variable.feature): You have a variable which you are not using.
-
-[UseBackground](https://github.com/BillyRuffian/chutney/blob/master/features/use_background.feature): You have a setup setup used in all of your scenarios. Move it to a Background section.
-
-[UseOutline](https://github.com/BillyRuffian/chutney/blob/master/features/use_outline.feature): You have very similar scenarios. You should consider if they should be combined into a Scenario Outline.

data/docs/usage/selective_enablement.md

@@ -1,14 +0,0 @@
----
-layout: default
-title: Selectively Disabling Rules
-parent: Usage
-nav_order: 4
----
-
-# Selectively Disabling Rules
-
-Sometimes you want to be able to disable linting rules for just one specific file or one specific scenario.
-
-To do this, use the tag format `@disable<Linter Name>`. For example `@disableTooLongStep`. 
-
-If used at the feature level, the linter will be deactivated for the whole file, used at the scenario level, only that one scenario will be excused.