Option to disable the fork behaviour

[LucaLanziani]

I'm using the library from a CI server to generate multiple files in the organization.
The CI is using the credential of a ci github user that is not part of the organization and I add this user as collaborator when it needs access to a specific repo.

The preferred behavior in this situation is to fail in case the user doesn't have push permission to the repo and not to fork it since no one will have access to this fork if not an admin.
Moreover the CI user might end up having many of the repos forked.

[gr2m]

Why would you have the CI user try to update files if it does not have the permission to do so?

[LucaLanziani]

A simple error in the configuration can cause that.
One person adds a new feature to the CI job to open a PR on repo xyz thinking permissions are ok while they are not.

Obviously I can catch this case before calling the createPullRequest if you prefer not to change the plugin behavior.

[gr2m]

I'd suggest you do that for the time being, I'd want to implement it for your case alone, it's too uncommon