Revalidate PRs from users whose profile is updated #26
Labels
Milestone
Comments
|
actually, the problem is a bit different than described: at the time where the status of the PR was set (assuming we're talking about PR 131 of IntersectionObserver), the user was indeed unknown to the system. Once you started adding them, they are no longer unknown; it happens that the PR is still not right since the user is not affiliated to the group, but if you were to revalidate the PR, I think it would show the right message. That being said, I think ideally, ash-nazg would revalidate automatically all the open PRs in which someone is a contributor when their info is created/updated. |
dontcallmedom
changed the title
dontcallmedom
added a commit
that referenced
this issue
Sep 21, 2020
…nt connection Allows to automatically revalidate any pending PR from the said github user Part of #26
deniak
added a commit
that referenced
this issue
Sep 22, 2020
…nt connection (#183) * Fix PR check for users not in a group without a non-participant commitment 'no commitment' made is not a status expected by the rest of the algorithm * Fix a typo * Add support for retrieving pull requests with unaffiliated contributors * Add supports for webhook endpoint coming from W3C API on github account connection Allows to automatically revalidate any pending PR from the said github user Part of #26 * Test new webhook endpoint for GH account connection * Fix another typo Co-authored-by: Denis Ah-Kang <deniak@users.noreply.github.com> Co-authored-by: Denis Ah-Kang <deniak@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
The system answers:
[[
User foobar is known to the system. You can edit that account.
]]
when the user pull request is classified as "unknown".
That's because the association with the W3C account is missing.
We should improve the message...
The text was updated successfully, but these errors were encountered: