You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which is why the second one rewards him. This would imply changing the whole logic to look at the originally assigned user to the issue from the PR and then consider the relationship to be ISSUE_ASSIGNED to override the PULL_COLLABORATOR. I do not know how v1 worked on this regard (with the bug it had it would reward everything regardless).
Overall, priority of statuses should be checked, and the highest relation status selected to apply the final rewards. In this scenario, since the user is ISSUE_ASSIGNEE at the time of the reward, that user should not be eligible for any reward.
The text was updated successfully, but these errors were encountered:
Keyrxng is:
ISSUE_ASSIGNEE
on Delete issues created by contributors ubiquity/devpool-directory-tasks#31PULL_AUTHOR
on fix: delete unauthorized issues ubiquity/devpool-directory#1341PULL_COLLABORATOR
on Prevent Unauthorized Users from creating issues in devpool ubiquity/devpool-directory#1330Which is why the second one rewards him. This would imply changing the whole logic to look at the originally assigned user to the issue from the PR and then consider the relationship to be
ISSUE_ASSIGNED
to override thePULL_COLLABORATOR
. I do not know how v1 worked on this regard (with the bug it had it would reward everything regardless).Originally posted by @gentlementlegen in ubiquity/devpool-directory-tasks#31 (comment)
Overall, priority of statuses should be checked, and the highest relation status selected to apply the final rewards. In this scenario, since the user is
ISSUE_ASSIGNEE
at the time of the reward, that user should not be eligible for any reward.The text was updated successfully, but these errors were encountered: