I am currently using an enterprise installation of GitHub and Jenkins, both of which are managed by another team so I have no control over plugin versions. It looks like there is a related issue to this (JENKINS-46068), but it is not quite the same thing as it deals with running jobs under both the old and new names after a rename. Not sure if the fix for that takes care of this request as well.

We use git tags and pipeline builds to manage deployment to several production environments and have requirements to rename several of our repositories. When we renamed the first one, it re-executed builds for all current branches and a significant number of tags, triggering conflicting deployments to multiple environments. Fortunately, that repository was a support library and we were able to correct the issues without an application outage.

We have several other repositories that need to be renamed and, at the moment, I have been unable to find a way to both rename the repositories and prevent Jenkins from re-executing pipelines on branches and tags which would cause unpredictable results in our environments and likely bring down a production application until we can sort the fallout.

The GitHub plugin needs to be able to detect a repository rename and, at minimum, do nothing. The ideal solution is for the plugin to migrate the job history from the old repository to the new so everything stays in sync between the tools.

I'm marking this as a Blocker because anyone using Jenkins for continuous delivery/deployment may be unable to rename repositories without impacting application operations.