Misleading error message when concern is left in a file comment

[samueltardieu]

The concern entered here was rejected with this message: "Only organization members can add or resolve concerns."

However, the problem was not organization membership, as the author was a member of rust-lang, but apparently that the concern was written in a file-specific comment. The error message is misleading.

Another (better?) resolution would be to accept concern registered in such messages.

Cc @ChrisDenton

[Urgau]

There is no fundamental reason it can't work with a pull-request review comment and the error message actually indicates that it tried adding the concern but failed for another reason.

The actual reason is the same as #2094, we use GitHub's author_association from the webhook response but since your membership status is "Private", it makes GitHub not report to us that you are part of the organization and thus we reject the command.

https://github.com/orgs/rust-lang/people?query=samu

Short-term solution is to put your membership status as "Public". Longer-term is for us (triagebot) to not us it anymore.

[samueltardieu]

Thanks @Urgau, I had no idea that my membership status for the rust-lang organization was private. I've switched it to public.