I am able to duplicate the bug with a unit test. It requires that I add a remote URL which is null. I am curious how your job is defined that it has a remote URL which is null. Can you provide more details on your job definition or your Jenkinsfile which might show how the remote URL of a repository is null?
I suspect that a null remote URL is not doing what you want, since the plugin can't clone from a repository that has a null remote URL. Possibly the URL definition has a trailing comma, or there is an additional repo defined which has an empty URL?
I'll submit a fix shortly.
I was unable to duplicate the problem on my initial interactive attempt. Steps I took:
- Define a GitHub Organization Folders job which monitors the MarkEWaite organization on github.com, watching the git-client-plugin repository
- Build the jobs that are defined
- Create a new pull request (PR17)
- Click the "Scan multi-branch pipeline" link in the git-client-plugin job, confirm that PR-17 is added as a job