Support for cloning private fork repositories in Frogbot pull request analysis

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

In our project, all contributors work on private fork repositories. When Frogbot analyzes a new pull request from the parent repository, it tries to clone the source repository. However, Frogbot lacks access rights to clone the private fork repository, which prevents it from analyzing the changes properly. This causes frustration as the analysis cannot be completed without additional access.

Describe the solution you'd like to see

It would be helpful if Frogbot could clone the pull request source directly, rather than the parent repository. This way, it could access the new changes in the private fork without requiring explicit access permissions to the forked repository. Ideally, the source repository URL used by Frogbot for cloning should be configurable.

Describe alternatives you've considered

Currently, we have no alternative other than granting broader access permissions to Frogbot, which is not ideal for security reasons. Another option could be manually syncing changes, but this is inefficient and error-prone.

Additional context

This feature would improve security and usability for projects where contributors use private forks. It would streamline Frogbot’s integration with pull request workflows involving private repositories.

Thank you very much for your time

The issue concerns Frogbot pull request analysis and cloning the pull request source repository; start by locating the cloning path used during analysis. Confirm the behavior for private fork URLs and define how a configurable source URL should be supplied, then verify analysis completes without granting Frogbot access to the fork.