Renaming a GitHub repository backing an Amplify app means you cannot reconnect it

[JamesMilnerAC]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• I have searched for duplicate or closed issues.
• I have removed any sensitive information from my code snippets and submission.

Amplify Hosting feature

Build settings

Is your feature request related to a problem? Please describe:

At the moment, for AWS Amplify apps if you rename your repository for the given application, it is not possible to reconnect the application in Amplify. If you go to Monitoring -> Branch Settings -> Reconnect repository you will receive a toast popup error. You can reproduce this by simply renaming an existing repo backing an Amplify app, then trying to reconnect it.

This is different to another request which is to change the underlying repository completely:
#4021

This issue is just specifically about renaming the existing repository on GitHub that backs the Amplify app.

Describe how you'd like this feature to work

1. Ideally, Amplify could understand when a repository has been renamed and automatically make the necessary changes to support the new name
2. If that's not possible, when you click Reconnect this works by updating the name to match the new repository name and updates any other references to the update repository name

[github-actions]

This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!

[bcmedeiros]

The connection is obviously broken, why is this a feature request?