Actions: add a note about auto-disable of scheduled workflows (#49545)

content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md

@@ -13,7 +13,7 @@ topics:
   - Workflows
   - Project management
 ---
- 
+
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 ## Introduction
@@ -66,7 +66,11 @@ In the tutorial, you will first make a workflow file that uses the [`actions/sta
 
 Based on the `schedule` parameter (for example, every day at 1:30 UTC), your workflow will find issues that have been inactive for the specified period of time and will add the specified comment and label. Additionally, your workflow will close any previously labeled issues if no additional activity has occurred for the specified period of time.
 
-{% data reusables.actions.schedule-delay %}
+{% note %}
+
+**Note:** {% data reusables.actions.schedule-delay %}
+
+{% endnote %}
 
 You can view the history of your workflow runs to see this workflow run periodically. For more information, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
 

content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md

@@ -97,7 +97,11 @@ In the tutorial, you will first make a workflow file that uses the {% data varia
 
 Based on the `schedule` parameter (for example, every Monday at 7:20 UTC), your workflow will create a new issue with the assignees, labels, title, and body that you specified. If you set `PINNED` to `true`, the workflow will pin the issue to your repository. If you set `CLOSE_PREVIOUS` to true, the workflow will close the most recent issue with matching labels.
 
-{% data reusables.actions.schedule-delay %}
+{% note %}
+
+**Note:** {% data reusables.actions.schedule-delay %}
+
+{% endnote %}
 
 You can view the history of your workflow runs to see this workflow run periodically. For more information, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
 

content/actions/using-workflows/events-that-trigger-workflows.md

@@ -1168,7 +1168,14 @@ jobs:
 | --------------------- | -------------- | ------------ | -------------|
 | Not applicable | Not applicable | Last commit on default branch | Default branch | When the scheduled workflow is set to run. A scheduled workflow uses [POSIX cron syntax](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). For more information, see "[AUTOTITLE](/actions/using-workflows#triggering-a-workflow-with-events)." |
 
-{% data reusables.actions.schedule-delay %}
+{% note %}
+
+**Notes:**
+
+- {% data reusables.actions.schedule-delay %}
+- In a public repository, scheduled workflows are automatically disabled when no repository activity has occurred in 60 days. For information on re-enabling a disabled workflow, see "[AUTOTITLE](/enterprise-server@3.12/actions/using-workflows/disabling-and-enabling-a-workflow#enabling-a-workflow)."
+
+{% endnote %}
 
 The `schedule` event allows you to trigger a workflow at a scheduled time.
 

data/reusables/actions/schedule-delay.md

@@ -1,5 +1 @@
-{% note %}
-
-Note: The `schedule` event can be delayed during periods of high loads of {% data variables.product.prodname_actions %} workflow runs. High load times include the start of every hour. If the load is sufficiently high enough, some queued jobs may be dropped. To decrease the chance of delay, schedule your workflow to run at a different time of the hour.
-
-{% endnote %}
+The `schedule` event can be delayed during periods of high loads of {% data variables.product.prodname_actions %} workflow runs. High load times include the start of every hour. If the load is sufficiently high enough, some queued jobs may be dropped. To decrease the chance of delay, schedule your workflow to run at a different time of the hour.