-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do Not Disqualify on Approval #57
Comments
Note The following contributors may be suitable for this task: gentlementlegen
|
/start |
! This task does not reflect a business priority at the moment. You may start tasks with one of the following labels: Priority: 3 (High), Priority: 4 (Urgent), Priority: 5 (Emergency) |
/help |
Available Commands
|
/wallet 0x226AAE6Db84dca652818400750b8BF96a077349e |
+ Successfully registered wallet address |
/start |
! This task does not reflect a business priority at the moment. You may start tasks with one of the following labels: Priority: 3 (High), Priority: 4 (Urgent), Priority: 5 (Emergency) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
daemon-merging doesn't have a chance to run properly if disqualifications happen on approved pulls. This should be fixed by halting the disqualifier logic once they received an approval.
Even if an argument is made around "increasing coupling" it still doesn't make sense to disqualify somebody after their deliverable has been approved, and there are delays from the other reviewers.
My gut feeling is that disqualification should continue to run on review states for "commented" and "request changes"
Perhaps in the future, a minor optimization could be to enforce that the conversations from the "commented" review must be resolved in order to halt disqualification, but this is easily gamed as I've seen assignees "resolve" comments without actually handling them. We would need to have more advanced logic to compare the diff with the review comments to see if they were actually addressed.
https://t.me/UbiquityDevPool/2990
Passed the deadline and no activity is detected, removing assignees: @kingsley-einstein.
Originally posted by @ubiquity-os[bot] in ubiquity/uusd.ubq.fi#1 (comment)
The text was updated successfully, but these errors were encountered: