[pull] main from github:main

.github/workflows/no-response.yaml

@@ -9,7 +9,7 @@ name: No Response
 
 on:
   issue_comment:
-    types: created
+    types: [created]
 
   schedule:
     # Schedule for five minutes after the hour every hour
@@ -27,4 +27,6 @@ jobs:
             to our request for more information from the original author. With only the
             information that is currently in the issue, we don't have enough information
             to take action. Please reach out if you have or find the answers we need so
-            that we can investigate further. See [this blog post on bug reports and the importance of repro steps](https://www.lee-dohm.com/2015/01/04/writing-good-bug-reports/) for more information about the kind of information that may be helpful.
+            that we can investigate further. See [this blog post on bug reports and the
+            importance of repro steps](https://www.lee-dohm.com/2015/01/04/writing-good-bug-reports/)
+            for more information about the kind of information that may be helpful.

.github/workflows/site-policy-sync.yml

@@ -1,8 +1,8 @@
 name: site-policy-sync
 
-# **What it does**: Updates our site policy docs when changes happen to site policy.
-# **Why we have it**: We want up to date site policy docs.
-# **Who does it impact**: Site policy team.
+# **What it does**: Updates our site-policy repo when changes happen to site policy docs.
+# **Why we have it**: We want keep site-policy repo up to date.
+# **Who does it impact**: Site-policy team.
 
 # Controls when the action will run.
 on:
@@ -30,6 +30,10 @@ jobs:
     steps:
       # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
       - uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
+      # Sets commit message
+      - name: custom message
+        run: |
+          echo "MESSAGE=${{github.event.pull_request.title}}" >> $GITHUB_ENV
 
       # Pushes to other repo
       - name: Push folder to another repository
@@ -42,6 +46,6 @@ jobs:
           destination_branch: 'main'
           destination_branch_create: 'repo-sync'
           destination_folder: 'Policies'
-          user_email: 'pcihon@users.noreply.github.com'
-          user_name: 'pcihon'
-          commit_msg: 'Automatic sync from GitHub Docs.'
+          user_email: 'site-policy-bot@users.noreply.github.com'
+          user_name: 'site-policy-bot'
+          commit_msg: '${{ env.MESSAGE }}'

content/admin/enterprise-management/increasing-storage-capacity.md

@@ -31,7 +31,10 @@ As more users join {% data variables.product.product_location %}, you may need t
 1. Resize the existing user volume disk using your virtualization platform's tools.
 {% data reusables.enterprise_installation.ssh-into-instance %}
 3. Put the appliance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
-4. Reboot the appliance to detect the new storage allocation.
+4. Reboot the appliance to detect the new storage allocation:
+  ```shell
+  $ sudo reboot
+  ```
 5. Run the `ghe-storage-extend` command to expand the `/data/user` filesystem:
   ```shell
   $ ghe-storage-extend
@@ -40,7 +43,10 @@ As more users join {% data variables.product.product_location %}, you may need t
 ### Increasing the root partition size using a new appliance
 
 1. Set up a new {% data variables.product.prodname_ghe_server %} instance with a larger root disk using the same version as your current appliance. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)."
-2. Shut down the current appliance.
+2. Shut down the current appliance:
+  ```shell
+  $ sudo poweroff
+  ```
 3. Detach the data disk from the current appliance using your virtualization platform's tools.
 4. Attach the data disk to the new appliance with the larger root disk.
 
@@ -57,6 +63,9 @@ As more users join {% data variables.product.product_location %}, you may need t
   ```shell
   $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
   ```
-4. Shut down the appliance.
+4. Shut down the appliance:
+  ```shell
+  $ sudo poweroff
+  ```
 5. In the hypervisor, remove the old root disk and attach the new root disk at the same location as the old root disk.
 6. Start the appliance.

content/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect.md

@@ -13,6 +13,7 @@ topics:
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
+{% data reusables.actions.enterprise-github-connect-warning %}
 {% data reusables.actions.ae-beta %}
 
 By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.product_name %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).

data/reusables/actions/enterprise-github-connect-warning.md

@@ -0,0 +1,7 @@
+{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "[email protected]" %}
+{% note %}
+
+**Note:** With {% data variables.product.prodname_github_connect %} enabled, {% data variables.product.prodname_actions %} will try to find the repository on your {% data variables.product.prodname_ghe_server %} instance first before falling back to {% data variables.product.prodname_dotcom %}. If a user creates an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom %}, the repository on your enterprise will be used in place of the {% data variables.product.prodname_dotcom %} repository. A malicious user could take advantage of this behavior to run code as part of a workflow.
+
+{% endnote %}
+{% endif %}