Closed 0x4007 closed 1 year ago
/assign
@harjaapdhillon16 The time limit for this bounty is on Mon, 05 Jun 2023 23:28:19 GMT
Your currently set address is:
0x9d4b1a2c56364532b6006d214dba3fe6e89da5ad
please use /wallet 0x4FDE...BA18
if you want to update it.
https://github.com/ubiquity/devpool-directory/pull/660 Raised a PR @pavlovcik
ubiquity/devpool-directory#660 Raised a PR @pavlovcik
@rndquu I just realized we can't directly associate these pull requests with the issues. Perhaps we should find a better setup for bounty hunters.
ubiquity/devpool-directory#660 Raised a PR @pavlovcik
@rndquu I just realized we can't directly associate these pull requests with the issues. Perhaps we should find a better setup for bounty hunters.
I've updated the description https://github.com/ubiquity/devpool-directory/pull/660#issue-1740674644 and the PR is linked now although this is a "cross repo" PR
@pavlovcik Can this issue be closed now , my PR has been approved !
0x9d4b1a2c...6e89da5ad
We should have a filter that indicates the current assignment status of a bounty. This way, bounty hunters can filter the view for only available bounties. It could be annoying and tedious if all the bounties they are interested in handling are taken. It takes a few clicks right now to view the status of the bounty.
Proposed solutions:
devpool-directory
mirror of the issue. This may lead to unnecessary notifications (or not!) but it will be the most direct way to express that the bounty is taken.Unavailable
Both solutions will allow bounty hunters to filter for only available bounties.