I appreciate this might be a limitation around GitHub API but when repository collaborators are empty, safe-settings won't modify the collaborators if an individual user has been added.
With this config, if a single collaborator (not a team) is given access manually it will go undetected, i.e. safe-settings will not remove the rogue collaborator.
What is the expected behavior
Manually added single collaborator is removed if not present in the settings.
Error output, if available
Context
Are you using the hosted instance of probot/settings or running your own?
If running your own instance, are you using it with github.com or GitHub Enterprise?
Problem Description
I appreciate this might be a limitation around GitHub API but when repository collaborators are empty, safe-settings won't modify the collaborators if an individual user has been added.
What is actually happening
Example config for repository
With this config, if a single collaborator (not a team) is given access manually it will go undetected, i.e. safe-settings will not remove the rogue collaborator.
What is the expected behavior
Manually added single collaborator is removed if not present in the settings.
Error output, if available
Context
Are you using the hosted instance of probot/settings or running your own?
If running your own instance, are you using it with github.com or GitHub Enterprise?
Version of probot/settings
Version of GitHub Enterprise