@jsoref
Thanks so much for opening an issue! I'll triage this for the team to take a look 👀

@jsoref - thanks for passing on this feedback on the docs from the support community ✨

It was particularly helpful to have the link to the discussion, where the potential security implications of an automatic redirect were raised.

I agree that this article should flag the fact that this is an exception to the general redirection of URLs following the renaming of a repository. I suggest we check in with the Actions team on the best practice for renaming a repository that hosts an action, before deciding on the change to make to the article.

Hi @jsoref - I checked in with the Actions team and their advice is that it in this situation, it's probably better for people to keep the old repository and create a new one with the new name, instead of renaming. I suggest that we make the following changes to the article.

Content update plan

Update the article on renaming repositories.

The tip from lines 39 to 43 is not needed now that the article states this permissions requirement just under the title in large text. So we can convert this into a note for people who maintain repositories that host actions.

1. Change the tip callout into a note callout (see Formatting callouts for the syntax).
2. Replace the current text in the callout with an explanation that if the repository hosts an action they should avoid renaming the repository. Instead they should create a new repository with the new name and deprecate the old repository. If they rename the repository, all workflows that use the action will fail with the error repository not found. The action is not automatically redirected when a workflow runs to avoid security issues.

@jsoref - Is this a change you were planning to make? If so, I'll leave this issue as is. If not, I'll update the issue summary with this content update plan and flag the issue as help wanted.

Thanks @felicitymay. I'm happy to leave this ticket for someone else to fix.