It is unlikely you have the legal ability to prohibit someone from publishing your contact details... _under copyright_. There may be other laws related to privacy that are relevant.
If the publisher in question is referring to "public domain", they probably have no idea what they're doing legally, "public domain" is unlikely to be relevant.
Practically, I would complain to Github itself, who is likely to frown at them doing that, and cut off their API access or what have you.
I've brought the issue to Github as well for them to judge whether there is any breach. They are best to decide I guess.
Far fewer laws about that exist than most people think, especially in the US. Some law and case law exists, but fairly narrowly. "Public disclosure of private information" doesn't apply here, since you posted the information publicly. "Intrusion of solitude" and "false light" don't apply. You could perhaps make a case for "appropriation" (using someone else's information for commercial gain without consent), but submitting that information to Github (and thus granting permission to Github under their terms, which they can choose to further grant to others) would negate that.
In any case, making legal threats doesn't seem likely to help here, and seems like overkill given the current state of the situation.
By the time lawyers get involved, which would be after the New Year, then the author might have already merged the PR and problem solved.
At the moment, it's simply a matter of discussion.
No urgency to push the developers to take action either.
I don't think that sentence describes any actually existing law in the US.
And yes, if the project refuses to fix this issue, contacting Github seems like the right next step.
Answered opaquely in terms of service:
> Customers may access their GitHub account data via an API (Application Program Interface)
My interpretation is that the "their" qualifier disallows people from using the API to access other people's data without proper authorization.
That interpretation wouldn't make sense with many well-established uses of Github's APIs today. For example, consider a CI service that tests incoming pull requests, and shows the details of each pull request, including the user who submitted it.
Showing appropriate user information in context (associated with their Github contributions), however, seems quite different from mass-scraping user information to create fake "claim me" accounts. Github may or may not want to allow that (and they can always change or clarify their position).
Legal issues aside, though, scraping another service to create pseudo-accounts and refusing to provide even an opt-out does not seem like a good business practice. While Gitpay appears to have done several things right that other services get wrong, this definitely isn't one of them, and it needs fixing.