From ad3d0cd9652281edc31418e1fa42ce9fa18acf93 Mon Sep 17 00:00:00 2001
From: Courtney Wilson <77312589+cmwilson21@users.noreply.github.com>
Date: Tue, 22 Mar 2022 05:38:44 -0500
Subject: [PATCH] Renaming repo workflow update #15575 (#16144)

---
 .../renaming-a-repository.md                                | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/repositories/creating-and-managing-repositories/renaming-a-repository.md b/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
index c089e88750..7d86a30d4d 100644
--- a/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
+++ b/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
@@ -36,11 +36,11 @@ If you plan to rename a repository that has a {% data variables.product.prodname
 
 {% endif %}
 
-{% tip %}
+{% note %}
 
-**Tip:** {% data reusables.organizations.owners-and-admins-can %} rename a repository. {% data reusables.organizations.new-repo-permissions-more-info %}
+**Note:** {% data variables.product.prodname_dotcom %} will not redirect calls to an action hosted by a renamed repository. Any workflow that uses that action will fail with the error `repository not found`. Instead, create a new repository and action with the new name and archive the old repository. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)."
 
-{% endtip %}
+{% endnote %}
 
 {% warning %}