[Improvement]: GHES scheduled-workflow docs show unsupported timezone syntax #23702 (#62591)

Author: am-stead

data/features/actions-schedule-timezone.yml

@@ -0,0 +1,6 @@
+# Scheduled workflows support timezones
+
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.22'

data/reusables/repositories/actions-scheduled-workflow-example.md

@@ -1,8 +1,12 @@
-Use [POSIX cron syntax](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07) to schedule workflows to run at specific times. By default, scheduled workflows run in UTC. You can optionally specify a timezone using an [IANA timezone string](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) for timezone-aware scheduling. Scheduled workflows run on the latest commit on the default branch. The shortest interval you can run scheduled workflows is once every 5 minutes.
+Use [POSIX cron syntax](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07) to schedule workflows to run at specific times. {% ifversion actions-schedule-timezone %}By default, scheduled workflows run in UTC. You can optionally specify a timezone using an [IANA timezone string](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) for timezone-aware scheduling{% else %}Scheduled workflows run in UTC{% endif %}. Scheduled workflows run on the latest commit on the default branch. The shortest interval you can run scheduled workflows is once every 5 minutes.
+
+{% ifversion actions-schedule-timezone %}
 
 > [!NOTE]
 > For schedules that set `timezone` to a time zone that observes daylight saving time (DST), during DST spring-forward transitions, scheduled workflows in skipped hours advance to the next valid time. For example, a 2:30 AM schedule advances to 3:00 AM.
 
+{% endif %}
+
 {% data reusables.repositories.cron %}
 
 You can use these operators in any of the five fields:
@@ -14,6 +18,8 @@ You can use these operators in any of the five fields:
 | - | Range of values | `30 4-6 * * *` runs at minute 30 of the 4th, 5th, and 6th hour. |
 | / | Step values | `20/15 * * * *` runs every 15 minutes starting from minute 20 through 59 (minutes 20, 35, and 50). |
 
+{% ifversion actions-schedule-timezone %}
+
 This example triggers the workflow to run at 5:30 AM in the America/New_York timezone every Monday through Friday:
 
 ```yaml
@@ -23,6 +29,8 @@ on:
       timezone: "America/New_York"
 ```
 
+{% endif %}
+
 A single workflow can be triggered by multiple `schedule` events. Access the `schedule` event that triggered the workflow through the `github.event.schedule` context. This example triggers the workflow to run at 5:30 UTC every Monday-Thursday, and 17:30 UTC on Tuesdays and Thursdays, but skips the `Not on Monday or Wednesday` step on Monday and Wednesday.
 
 ```yaml