From 5f8074e677ae0ab79431881083a02037a515d709 Mon Sep 17 00:00:00 2001 From: Tim Rogers Date: Tue, 5 Sep 2023 08:24:53 +0100 Subject: [PATCH] Document that GitHub Actions scheduled workflows won't work automatically after a `ghe-migrator` import (#41804) Co-authored-by: Matt Pollard --- .../migrating-data-to-github-enterprise-server.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/migrations/using-ghe-migrator/migrating-data-to-github-enterprise-server.md b/content/migrations/using-ghe-migrator/migrating-data-to-github-enterprise-server.md index bb288f2d8b22..60545bc9d4f7 100644 --- a/content/migrations/using-ghe-migrator/migrating-data-to-github-enterprise-server.md +++ b/content/migrations/using-ghe-migrator/migrating-data-to-github-enterprise-server.md @@ -130,6 +130,12 @@ After your migration is applied to your target instance and you have reviewed th {% data reusables.enterprise_installation.ssh-into-instance %} {% data reusables.enterprise_migrations.unlocking-on-instances %} +{% warning %} + +**Warning:** If your repository contains {% data variables.product.prodname_actions %} workflows using the `schedule` trigger, the workflows will not run automatically after an import. To start the scheduled workflows once again, push a commit to the repository. For more information, see "[AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows#schedule)." + +{% endwarning %} + ## Unlocking repositories on the source ### Unlocking repositories from an organization on {% data variables.product.prodname_dotcom_the_website %}