Contact repository owner

We have an organization with ~200 people in it and more than 200 repositories (I’m one of the organization admins).
I need to be able to contact those people or at least the reposity owners (preferably by email). When we were inviting them we were also adding their usernames with the corresponding emails to an excel spreadsheet, but lost it.
And now for some users that have usernames that are not their real names we cannot relly know who’s behind that repository… How can we understand the repositry owner’s email address (or contact them in another way)?

1 Like

Hi @Tonipetrov , welcome to the community

Unfortunately there is no direct messaging feature in GitHub that I am aware of
Some options that may reveal a contact are below

  1. if they made their mail public on their profile.
  2. (search the page for “email”), if they used their public email in commits
  3. You could try reaching out to them in an issue in their repository
  4. For a SAML enabled organization (for a linked member not an outside collaborator) you will be able to derive from the linked identity in you IdP. But from your description this will not apply for your case.

Good luck.

1 Like


Brilliant! Thanks.

What would happen if you created an issue in your own repo and then @mentioned the user you want to reach? Would he receive a notice that he was mentioned?

I don’t think you can @mention any GitHub user account who is not related to or a member of the repository an issue belongs to?
A user has to be listening to notifications and responding for this approach to be of any use as well.

The workaround we came up eventually was:

  1. Add all people we couldn’t identify to a new team we created and named “Unidentified”
  2. Wrote a message in GitHub to that team (mentioned it) that since we cannot identify them we will remove them from the oranization unless they send us an email saying something like “This is my github username related to that email address”.

Some of them contacted us, the other we cleaned up. I can say that worked in our case.

1 Like

There is that “no-reply” email that every GitHub user has. I wonder if anything could be done with that :face_with_raised_eyebrow: