Feat/max bounty issue improvement fixed

[wannacfuture]

Description

• added feat: max bounty issue improvement(counts opened prs with no reviews)

closes #298

[netlify]

✅ Deploy Preview for ubiquibot-staging ready!

Name	Link
🔨 Latest commit	ca0ae35
🔍 Latest deploy log	https://app.netlify.com/sites/ubiquibot-staging/deploys/64834e65de0ad50008b66fd8
😎 Deploy Preview	https://deploy-preview-387--ubiquibot-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[0x4007]

Code looks good. You achieved the specification, thanks for that, but I think I will like to create a new bounty to make the 24 hour period configurable (this also means we need to add a new config property.

[wannacfuture]

Code looks good. You achieved the specification, thanks for that, but I think I will like to create a new bounty to make the 24 hour period configurable (this also means we need to add a new config property.

Could you provide me detailed information? If you create another new bounty about it, I'll also handle it.

[0x4007]

If our new standard operating procedure is to request a QA test from @Draeieg then the last person to approve (@0xcodercrane) should request for a review from @Draeieg after the code checks out.

[wannacfuture]

Seems your new standard operating procedure is too perfect.😅 @Draeieg , Could you review this PR?

[Draeieg]

Seems your new standard operating procedure is too perfect.😅 @Draeieg , Could you review this PR?

I need @0xcodercrane merge this to development in order to do my QA run

Also, we're going to implement #391, reducing the bureaucracy

[wannacfuture]

Ah.. so, should I install QA app to my forked repo? And what should I do?
I can't get that meaning exactly. Could you explain in detail?

[Draeieg]

Ah.. so, should I install QA app to my forked repo? And what should I do?
I can't get that meaning exactly. Could you explain in detail?

The current plan is: Install the QA app on your forked repo, run the github action, and you should have the bot running with local changes

Then, open issues to test the code changes (by example in this case, you can open 3 assign to 2 then request for a review from yourself and then see if you can assign the third)

We're literally just releasing this, so if something sounds confusing or is not working, be sure to notify

[wannacfuture]

Ah.. so, should I install QA app to my forked repo? And what should I do?
I can't get that meaning exactly. Could you explain in detail?

The current plan is: Install the QA app on your forked repo, run the github action, and you should have the bot running with local changes

Then, open issues to test the code changes (by example in this case, you can open 3 assign to 2 then request for a review from yourself and then see if you can assign the third)

We're literally just releasing this, so if something sounds confusing or is not working, be sure to notify

Actually, I have tested my PR on my local repository(not forked repo) and it worked. I installed QA app to that repository.

You can see the test result on https://github.com/wannacfuture/Battleship.
There, there are 4 issues and I assigned 3 issues even the maximum issue count is 2 because I have one Pull Request which is created over 24 hours before. And fourth assign was failed. It works correctly. @Draeieg , Could you review that one?