chore: hide unavailable bounties

[Keyrxng]

Resolves ubiquity/devpool-directory-tasks#11

• https://github.com/Keyrxng/devpool-directory/issues
• https://github.com/Keyrxng/devpool-directory/issues/34

I'm currently assigned the dynamic rpc handler task so in my forked devpool repo it's closed

[0x4007]

@Keyrxng as a heads up I'm sort of stepping away from code reviews these days, so that I can spend more time on recruiting and fundraising. In the short term I plan to just stay on top of conversations at a high level in order to remedy any operational blockers during this transition phase.

In this situation I think you should request for reviews until we figure out who will be the de-facto "manager" of this repository, although I would default to rndquu if I'm not sure for most cases.

[Keyrxng]

I hope that's a good thing for you but cheers mate I'll ping rndquu or paul from now on

[rndquu]

Overall, when this PR is merged we're free to remove the "Unavailable label" feature since all of the open issues in the devpool will be available for self-assignment

[Keyrxng]

https://github.com/Keyrxng/devpool-directory/issues/32

[rndquu]

@Keyrxng Pls notice that requested changes are not implemented

[Keyrxng]

@Keyrxng Pls notice that requested changes are not implemented

I was thinking wth I did make the changes, but after checking I realize I forgot to push lmao

[rndquu]

Works fine

[Keyrxng]

@rndquu should the checks against the unavailable labels be removed? I think that's what's causing the open/close cycle that's happening right now.

Looking at the logs

second most recent run:

Closed (assigned): https://github.com/ubiquity/devpool-directory/issues/1125 (https://github.com/ubiquity/pay.ubq.fi/issues/196)

most recent run:

Updated: https://github.com/ubiquity/devpool-directory/issues/1125 (https://github.com/ubiquity/pay.ubq.fi/issues/196)

with "Updated: ..." it's happening outside of the two conditionals I added, and you said that there's no need to check those labels and they'll be getting removed anyway?

• devpool-directory/index.ts

  Line 139 in a73a14f

  (!isDevpoolUnavailableLabel && projectIssue.assignee?.login) ||

[0x4007]

@Keyrxng test on your fork then to prove that its a solution. I would consider this problem urgent because it negatively affects new people coming to work.ubq.fi to see if they want to work with us.

[rndquu]

@rndquu should the checks against the unavailable labels be removed?

Yes

with "Updated: ..." it's happening outside of the two conditionals I added, and you said that there's no need to check those labels and they'll be getting removed anyway?

Yes

Related issue ubiquity/devpool-directory-tasks#22

[Keyrxng]

Only just seeing this now, my notifications got tanked after I chose only the day before yesterday to subscribe to devpool notifications lmao. I'll test it before pushing