Remove outside collaborators with read role from public repository while circumventing API side effects

[EHJ-52n]

Select Topic Area

Question

Body

I want to clean-up our organization outside collaborators. I have many public repositories with many outside collaborators having just the read role. This seems useless to me because the repositories are public, hence anyone has read permission. These role assignments create a lot of noise and I want to remove them. But, when removing the permission via API, not only the permission will be removed, but:

This endpoint also:

• Cancels any outstanding invitations
• Unasigns the user from any issues
• Removes access to organization projects if the user is not an organization member and is not a collaborator on any other organization repositories.
• Unstars the repository
• Updates access permissions to packages

Removing a user as a collaborator has the following effects on forks:

• If the user had access to a fork through their membership to this repository, the user will also be removed from the fork.
• If the user had their own fork of the repository, the fork will be deleted.
• If the user still has read access to the repository, open pull requests by this user from a fork will be denied.

Source: https://docs.github.com/en/rest/collaborators/collaborators?apiVersion=2022-11-28#remove-a-repository-collaborator

I made the actions, that I find problematic, bold.

Is there any way to circumvent these side effects?