Merge pull request #5551 from github/repo-sync

repo sync

Author: Octomerger

content/actions/guides/about-continuous-integration.md

@@ -53,6 +53,7 @@ For a definition of common terms, see "[Core concepts for {% data variables.prod
 
 Browse the complete list of CI workflow templates offered by {% data variables.product.product_name %} in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}.
 
+{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}
 ### Skipping workflow runs
 
 If you want to temporarily prevent a workflow from being triggered, you can add a skip instruction to the commit message. Workflows that would otherwise be triggered `on: push` or `on: pull_request`, won't be triggered if you add any any of the following strings to the commit message in a push, or the HEAD commit of a pull request:
@@ -72,6 +73,7 @@ You won't be able to merge the pull request if your repository is configured to
 **Note:** Skip instructions only apply to the `push` and `pull_request` events. For example, adding `[skip ci]` to a commit message won't stop a workflow that's triggered `on: pull_request_target` from running.
 
 {% endnote %}
+{% endif %}
 
 ### Notifications for workflow runs
 

content/admin/configuration/about-enterprise-configuration.md

@@ -17,9 +17,7 @@ topics:
 {% endif %}
 
 {% if currentVersion == "github-ae@latest" %}
-The first time you access your enterprise, you will complete an initial configuration to get {% data variables.product.product_name %} ready to use. The initial configuration includes connecting your enterprise with an idP, authenticating with SAML SSO, and configuring policies for repositories and organizations in your enterprise. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
-
-For users to receive any emails from {% data variables.product.product_name %} after the initial configuration, you must ask {% data variables.contact.github_support %} to configure outbound email support with your SMTP server. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-email-for-notifications)."
+The first time you access your enterprise, you will complete an initial configuration to get {% data variables.product.product_name %} ready to use. The initial configuration includes connecting your enterprise with an identity provider (IdP), authenticating with SAML SSO, configuring policies for repositories and organizations in your enterprise, and configuring SMTP for outbound email. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)."
 
 Later, you can use the site admin dashboard and enterprise settings to further configure your enterprise, manage users, organizations and repositories, and set policies that reduce risk and increase quality. 
 
@@ -29,4 +27,4 @@ All enterprises are configured with subdomain isolation and support for TLS 1.2
 ### Further reading
 
 - "[Managing users, organizations, and repositories](/admin/user-management)"
-- "[Setting policies for your enterprise](/admin/policies)"
+- "[Setting policies for your enterprise](/admin/policies)"

content/admin/configuration/initializing-github-ae.md

@@ -103,11 +103,11 @@ Once this is initialized, you can reconfigure any settings after the initializat
  settings to allow incoming emails](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)."
   !["Enable" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-enable-email-configure.png)
 3. Complete your email server settings:
-  - In the **Server address** field, type the address of your SMTP server.
-  - In the **Port** field, type the port that your SMTP server uses to send email.
-  - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any.
-  - In the **Authentication** dropdown, choose the type of encryption used by your SMTP server.
-  - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails.
+    - In the **Server address** field, type the address of your SMTP server.
+    - In the **Port** field, type the port that your SMTP server uses to send email.
+    - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any.
+    - In the **Authentication** dropdown, choose the type of encryption used by your SMTP server.
+    - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails.
 
 4. If you want to discard all incoming emails that are addressed to the no-reply email address, select **Discard email addressed to the no-reply email address**.
   !["Discard" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-discard-email.png)