Max bounty hunter issues improvement

[0x4007]

An improvement idea is to check all of the open pull requests of the bounty hunter, and then check the state of the pull request review.

If they have a pull request open but no review started, then it counts against their quota.

If they have a pull request opened and also have a "review" in progress (perhaps there is an api to get a Boolean for this) then they are able to start working on another bounty.

Next level beyond could be a
one day "cool down". If there's longer than a 24 hour delay by the core team/reviewers, then "unlock" the bounty hunter to work on another issue.

Originally posted by @pavlovcik in #245 (comment)

[wannacfuture]

Let's clarify.

If a bounty hunter has opened pull request with no review, then the value of available_bounty_hunter_issue will decrease.(the initial value of available_bounty_hunter_issue will be max_bounty_hunter_issue config).

However, if the bounty hunter has opened pull request with no review, but the pull request is created more than 24 hours ago, then the value of available_bounty_hunter_issue will increase.

When the bounty hunter assigns themselves to an issue, the bot will calculate their available_bounty_hunter_issue value. If this value is zero, the bot will add a comment saying: "You cannot assign yourself to this issue because you have other open pull requests.".

In conclusion, I need to calculate only opened PR numbers with no review which is created within 24hours before.

Am i right?

[wannacfuture]

/start

[ubiquibot]

@wannacfuture The time limit for this bounty is on Fri, 09 Jun 2023 18:49:43 GMT

Your currently set address is:
0x9e4EF4353C928cD3eb473E8f12aeCF58C208ef40
please use /wallet 0x4FDE...BA18 if you want to update it.

[ubiquibot]

[ CLAIM 150 WXDAI ]

0x9e4EF435...8C208ef40