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

Repo sync

content/contributing/syntax-and-versioning-for-github-docs/using-markdown-and-liquid-in-github-docs.md

@@ -302,6 +302,16 @@ Reusable strings (commonly called content references or conrefs) contain content
 
 For longer strings, we use reusables, and for shorter strings, we use variables. For more information about reusables and variables, see "[AUTOTITLE](/contributing/writing-for-github-docs/creating-reusable-content)."
 
+## Table pipes
+
+Every row of a table in the {% data variables.product.prodname_docs %} must start and end with a pipe, `|`.
+
+```markdown
+| Where is the table located? | Does every row end with a pipe? |
+| --- | --- |
+| GitHub Docs | Yes |
+```
+
 ## Table row headers
 
 If you create a table where the first column contains headers for the table rows, wrap your table in the Liquid tag {% raw %}`{% rowheaders %} {% endrowheaders %}`{% endraw %}. For more information on using markup for tables, see "[AUTOTITLE](/contributing/writing-for-github-docs/style-guide#use-proper-markup-for-row-and-column-headers)."

content/contributing/writing-for-github-docs/style-guide.md

@@ -951,6 +951,8 @@ TEXT
 
 ## Tables
 
+Tables are added to the {% data variables.product.prodname_docs %} using Markdown. Because tables can be challenging to read and maintain, make sure that the data in a table is best represented in a table and not another format, like a list, before creating a table. Every row in a table must begin and end with a pipe, `|`.
+
 ### Use tables only for presenting tabular information
 
 Tables work best for presenting tabular data, such as information that needs to be compared or values with multiple attributes. Do not use tables for simple lists - see the "[Lists](#lists)" section of this document.

src/audit-logs/lib/config.json

@@ -1,3 +1,3 @@
 {
-  "sha": "014ee19105fa3d00686ecb66731fe68aa3e7e8cd"
+  "sha": "a9c6b05784cb6785a49d9d120bf25a7dd4e75f02"
 }