gh_collab_invite() appears to default to inviting users with WRITE access

[charliejhadley]

It appears that gh_collab_invite() defaults to inviting users with write access.

I wonder if a better default would be "read" access?

[jdtrat]

Hi! Thanks for bringing this up. I've been meaning to revisit this package and add some new features, and this is definitely something I can look into. I'm hesitant to change the default behavior, though. Would specifying an environmental option work? Something like ghee.default.collab.permission that I could check for internally?

Also, are you working with a GitHub Organization? If so, from the API documentation, it looks like you can specify the collaborator's permissions (described here). I typically use this function for non-organization collaborations, and the default permission is "push", but that can be changed to one of c("pull", "push", "admin", "maintain", "triage") by passing that as an argument to gh_collab_invite() (perhaps writing a custom wrapper would be an alternative solution for the time being, too?).

[charliejhadley]

I was using this within a GitHub organisation to automate inviting folks as they filled in an online form with their github username. An argument to gh_collab_invite() with these options would work, I think