ADD TO: publish action / auto-generate table of contents

Author: jrfnl

wiki/Coding-Standard-Tutorial.md

@@ -2,6 +2,13 @@ In this tutorial, we will create a new coding standard with a single sniff. Our
 
 Sniffs need to follow [strict directory layout and naming conventions](https://github.com/PHPCSStandards/PHP_CodeSniffer/wiki/About-Standards-for-PHP_CodeSniffer#naming-conventions).
 
+## Table of contents
+
+<!-- START doctoc -->
+<!-- END doctoc -->
+
+***
+
 ## Creating the Coding Standard Directory
 
 All sniffs in PHP_CodeSniffer must belong to a coding standard. A coding standard is a directory with a specific sub-directory structure and a `ruleset.xml` file, so creating a standard is straight-forward.

wiki/Version-4.0-Developer-Upgrade-Guide.md

@@ -96,7 +96,7 @@ Support for the JS/CSS tokenizers has been removed. To cause the least amount of
 
 This has been implemented in this way to allow external standards to be cross-version compatible with PHPCS 3.x as well as 4.x for a while and to not force external standards to release a new major release to support PHPCS 4.0 (due to sniffs needing to be removed).
 
-#### Upgrading
+**Upgrading**
 
 Search for sniffs which specify the `public $supportedTokenizers` property to find sniffs which may need updating.
 
@@ -118,7 +118,7 @@ Type casting for sniff property values set from within a ruleset has been made m
 * `null` will now be set to an actual `null` value. Previously, the sniff property would have been set to string `'null'`.
 * Array element values will now also get the type casting treatment. Previously, array values would always be strings.
 
-#### Upgrading
+**Upgrading**
 
 Search for sniff which have `public` properties which can be changed from within a ruleset.
 
@@ -406,7 +406,7 @@ The `AbstractPatternSniff::__construct()` method no longer takes any arguments.
 Since PHPCS 1.4.0, the  AbstractPatternSniff sets the `ignoreComments` option using a `public` var rather than through the constructor.  
 This allows the setting to be overwritten in `ruleset.xml` files.
 
-#### Upgrading
+**Upgrading**
 
 * Search for sniffs which extend the `AbstractPatternSniff`.
 * If the sniff calls the `parent::__construct()` method with an argument, remove the argument.
@@ -533,7 +533,7 @@ The `protected` `getDeclarationNameWithNamespace()` and `getNamespaceOfScope()`
 
 The Ruleset class now respects sniff selection via `--sniffs=...`, even when in a test context.
 
-#### Upgrading
+**Upgrading**
 
 If your own test framework contained work-arounds to get round the previous restriction, it should now be safe to remove those work-arounds and to use the `--sniffs=...` argument when initiating the `Config` class.
 
@@ -585,7 +585,7 @@ If an external standard uses its own test framework, this section can be skipped
 For compatibility with the PHP_CodeSniffer native test framework, the directory layout conventions and class naming conventions for tests have to be strictly followed and external standards which want to use the PHPCS native test framework need to be registered in the PHP_CodeSniffer `CodeSniffer.conf` file.
 This is not really any different from before, just even more important now.
 
-#### Upgrading
+**Upgrading**
 
 In practice this means the following for most test suites for external standards which extend the PHP_CodeSniffer native test suite:
 1. In `composer.json`: update the PHPUnit version requirements.