Github Discussions and Teams

I’m pretty interested in Github Discussions, however, I have a problem with the Teams.

I have a number of 3rd parties we work with, and have made Teams for them. If I leave them as-is, they can see Discussions which we don’t make Private.

If I convert the users to external collaborators, the penalty is pretty steep:

Converting members to outside collaborators will remove them from this organization and from all teams.

Their repository access will be preserved by making them collaborators on all repositories that their teams gave them access to. They will retain access to repositories that they were previously collaborators on, but all other access to this organization’s repositories will be lost.

It means I’ll loose track of who’s from which development partner of ours, and they may lose access to repos.

Has anyone else run across this? What are you doing about it?

At this point, we’re basically not using Discussions bc it’s too easy to leave a post public, which is a drag because I think it’s a great feauture.

Bumping this message to see what others are doing.

https://github.com/blog/2471-introducing-team-discussions

Hi @yesthatallen I wanted to comment here and just acknowledge the difficulty you’re having with 3rd parties on your Teams and the privacy of Discussions.

Though we don’t have a built in way to do this at this time, I want to let you know that we’re passing this feedback on to the appropriate teams for future consideration on newer iterations of the Discussions feature in the future. 

Thank you for being a part of the GitHub Community Forum; we’re glad you’re here.

Cheers!

2 Likes