From 288229130f239ee98fc02dde265ef7f9558cb2e0 Mon Sep 17 00:00:00 2001 From: Joe Clark <31087804+jc-clark@users.noreply.github.com> Date: Wed, 18 Oct 2023 08:47:15 -0700 Subject: [PATCH 1/2] Update beta note for GitHub Actions required workflows deprecation (#44138) Co-authored-by: Siara <108543037+SiaraMist@users.noreply.github.com> --- data/reusables/actions/workflows/required-workflow-beta.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/actions/workflows/required-workflow-beta.md b/data/reusables/actions/workflows/required-workflow-beta.md index 2ca3683297..30265e69ac 100644 --- a/data/reusables/actions/workflows/required-workflow-beta.md +++ b/data/reusables/actions/workflows/required-workflow-beta.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Required workflows for {% data variables.product.prodname_actions %} are in private beta and are not available for new sign ups.{% ifversion repo-rules-required-workflows %} On October 18th, 2023, you will no longer be able to access required workflows for {% data variables.product.prodname_actions %} and must use repository rulesets instead. You can read more about this change on the [{% data variables.product.company_short %} blog](https://github.blog/changelog/2023-08-02-github-actions-required-workflows-will-move-to-repository-rules/). For more information about repository rulesets, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets#require-workflows-to-pass-before-merging)."{% endif %} +**Note:** {% data variables.product.company_short %} is deprecating support for required workflows for {% data variables.product.prodname_actions %}.{% ifversion repo-rules-required-workflows %} You must use repository rulesets instead. For more information about repository rulesets, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets#require-workflows-to-pass-before-merging)." You can read more about this change on the [{% data variables.product.company_short %} blog](https://github.blog/changelog/2023-08-02-github-actions-required-workflows-will-move-to-repository-rules/).{% endif %} {% endnote %} From 9cc881e75d6bf5d7c98cd0f4db13ef1a0bc4a59f Mon Sep 17 00:00:00 2001 From: Begona Guereca Date: Wed, 18 Oct 2023 09:04:02 -0700 Subject: [PATCH 2/2] Update migrating-from-bamboo-with-github-actions-importer.md (#44580) Co-authored-by: Siara <108543037+SiaraMist@users.noreply.github.com> --- .../migrating-from-bamboo-with-github-actions-importer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/migrating-to-github-actions/automated-migrations/migrating-from-bamboo-with-github-actions-importer.md b/content/actions/migrating-to-github-actions/automated-migrations/migrating-from-bamboo-with-github-actions-importer.md index 1d87f8c244..e226f1fb2a 100644 --- a/content/actions/migrating-to-github-actions/automated-migrations/migrating-from-bamboo-with-github-actions-importer.md +++ b/content/actions/migrating-to-github-actions/automated-migrations/migrating-from-bamboo-with-github-actions-importer.md @@ -42,7 +42,7 @@ There are some limitations when migrating from Bamboo to {% data variables.produ - Pattern match labeling is not transformed because there is no equivalent in {% data variables.product.prodname_actions %}. - All artifacts are transformed into an `actions/upload-artifact`, regardless of whether they are `shared` or not, so they can be downloaded from any job in the workflow. - Permissions are not transformed because there is no suitable equivalent in {% data variables.product.prodname_actions %}. -- {% data variables.product.prodname_actions_importer %} supports Bamboo version between 7.1.1 and 8.1.1, however, project and plan variables will not be migrated. +- If the Bamboo version is between 7.1.1 and 8.1.1, project and plan variables will not be migrated. #### Manual tasks