Merge pull request github#28490 from github/repo-sync

Repo sync

content/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md

@@ -21,6 +21,12 @@ topics:
   - Upgrades
 shortTitle: Migrate from 11.10.x to 2.1.23
 ---
+{% note %}
+
+**Note**: {% data variables.product.prodname_ghe_server %} 11.10 is an unsupported release from 2014. For a list of supported releases, see "[AUTOTITLE](/admin/all-releases)."
+
+{% endnote %}
+
 Migrations from {% data variables.product.prodname_enterprise %} 11.10.348 and later are supported. Migrating from {% data variables.product.prodname_enterprise %} 11.10.348 and earlier is not supported. You must first upgrade to 11.10.348 in several upgrades. For more information, see the 11.10.348 upgrading procedure, "[Upgrading to the latest release](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/)."
 
 To upgrade to the latest version of {% data variables.product.prodname_enterprise %}, you must first migrate to {% data variables.product.prodname_ghe_server %} 2.1, then you can follow the normal upgrade process. For more information, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)".

content/contributing/collaborating-on-github-docs/using-the-content-linter.md

@@ -141,3 +141,31 @@ These rules should be fixed before merging content into the `main` branch, but t
 | [GHD001](https://github.com/github/docs/blob/main/src/content-linter/lib/linting-rules/code-fence-line-length.js) | Code fence content should be 60 lines or less in length. |
 | [GHD003](https://github.com/github/docs/blob/main/src/content-linter/lib/linting-rules/image-alt-text-length.js) | Images alternate text should be between 40-150 characters. |
 | [GHD004](https://github.com/github/docs/blob/main/src/content-linter/lib/linting-rules/internal-links-slash.js) | Internal links must start with a `/`. |
+
+## Suppressing linter rules
+
+Rarely, you may need to document something that violates one or more linter rules. In these cases, you can suppress rules by adding a comment to the Markdown file. You can disable all rules or specific rules. Always try to limit as few rules as possible.
+
+<!-- markdownlint-disable MD011 -->
+For example, if you are writing an article that includes a regular expression such as <code>(^|/)[Cc]+odespace/</code>, you can suppress the `MD011` rule that checks for reversed link syntax by adding the following comment.
+
+<pre>
+&lt;!-- markdownlint-disable MD011 --&gt;
+(^|/)[Cc]+odespace/
+&lt;!-- markdownlint-enable MD011 --&gt;
+</pre>
+
+<!-- markdownlint-enable MD011 -->
+
+You can use these comments to enable or disable rules.
+
+| Comment | Effect |
+| :-- | :-- |
+| <pre>&lt;!-- markdownlint-disable --&gt;</pre> | Disable all rules |
+| <pre>&lt;!-- markdownlint-enable --&gt;</pre> | Enable all rules |
+| <pre>&lt;!-- markdownlint-disable-line --&gt;</pre> | Disable all rules for the current line |
+| <pre>&lt;!-- markdownlint-disable-next-line --&gt;</pre> | Disable all rules for the next line |
+| <pre>&lt;!-- markdownlint-disable RULE-ONE RULE-TWO --&gt;</pre> | Disable one or more rules by name |
+| <pre>&lt;!-- markdownlint-enable RULE-ONE RULE-TWO --&gt;</pre> | Enable one or more rules by name |
+| <pre>&lt;!-- markdownlint-disable-line RULE-NAME --&gt;</pre> | Disable one or more rules by name for the current line |
+| <pre>&lt;!-- markdownlint-disable-next-line RULE-NAME --&gt;</pre> | Disable one or more rules by name for the next line |