add guidance on scheduled workflow examples (github#18417)

Sarah Edwards · web-flow · commit e214f65cb5f3 · 2021-03-25T21:16:32.000Z
diff --git a/contributing/content-style-guide.md b/contributing/content-style-guide.md
@@ -13,6 +13,7 @@ These guidelines are specific to GitHub’s documentation. For general style que
   - [Commands](#commands)
   - [Examples](#examples)
   - [Indentation](#indentation)
+  - [Scheduled workflows](#scheduled-workflows)
 - [Headers](#headers)
 - [Images](#images)
   - [Alt text](#alt-text)
@@ -145,6 +146,14 @@ In YAML examples, such as actions and workflow files, use two spaces to indent l
           python-version: ${{ matrix.python }}
 ```
 
+### Scheduled workflows
+
+Workflow runs are delayed when too many workflows run at once. Since many users copy code from the GitHub docs, we should use examples that guide users away from congested times.
+
+- Do not use examples that run on the hour. (The Actions team reports that times at the start of the hour, especially UTC midnight, are disproportionately overloaded.)
+- Do not use examples that run more frequently than necessary. For example, instead of running every 5 minutes, consider if the example makes sense to run every 30 minutes instead.
+- Use a different time for each example.
+
 ## Headers
 
 Use H3 for headers, and H4 for subheaders. When referring to headers, surround the header name with quotation marks.
