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
{{ message }}
This repository has been archived by the owner on Sep 19, 2024. It is now read-only.
We want to be able to efficiently process slow moving reviews and not invest reviewers' time and energy on slow moving pull requests.
Proposal
When the comment incentives for all of the requested reviewers maxes out (e.g. the bounty is Price: 100 USD, and reviewer A accrued 100 USD and reviewer B accrued 100 USD in incentives, then the bot should automatically close the pull request with a comment stating that there are no more incentives available for the reviewers to continue working on this pull request. Most importantly, no permits should be generated for the issue because it was not closed as completed.
This should clearly signal to the bounty hunter that the task took too long.
They would need to manually unassign themselves from the task in order to work on a new task.
This allows the opportunity for a reviewer (e.g. myself) to reopen the pull request if it is super close to being done, to allow the bounty hunter to complete it, even though I receive no additional financial incentives to continue helping with the review.
Once the task is completed, the payment permits are generated for all contributors.
The text was updated successfully, but these errors were encountered:
Context
We want to be able to efficiently process slow moving reviews and not invest reviewers' time and energy on slow moving pull requests.
Proposal
When the comment incentives for all of the requested reviewers maxes out (e.g. the bounty is
Price: 100 USD
, and reviewer A accrued100 USD
and reviewer B accrued100 USD
in incentives, then the bot should automatically close the pull request with a comment stating that there are no more incentives available for the reviewers to continue working on this pull request. Most importantly, no permits should be generated for the issue because it was not closed as completed.The text was updated successfully, but these errors were encountered: