feat: update index

[BeanieMen]

Resolves #11

[0x4007]

Code looks fine @rndquu what do you think is the easiest way we can test that this works?

@BeanieMen do you have any evidence to prove that this works as expected?

[BeanieMen]

Code looks fine @rndquu what do you think is the easiest way we can test that this works?

@BeanieMen do you have any evidence to prove that this works as expected?

Can I wait to see what rndquu says about testing

[BeanieMen]

/wallet 0x24fbA1343132DE969Aeef0B1BD5CaAE1fB102978

[ubiquibot]

+ Successfully registered wallet address

[rndquu]

@BeanieMen Pls:

1. Fix the issues in comments
2. Provide a QA (links to 3 issues) for 3 cases described in the original issue Hide unavailable bounties devpool-directory-tasks#11

[BeanieMen]

case 1 This wasnt synced
case 2 this closed because it was unavailable
case 3 this reopened even tho i closed it

[BeanieMen]

it shows i was the one who did the actions, i used my GITHUB_TOKEN because i ran the script using tsx

[BeanieMen]

yay it finally works.

[BeanieMen]

case 1 was never synced
case 2 was closed automatically because it was unavailable
case 3 the opened automatically because it was available and closed

[gitcoindev]

/query @BeanieMen

[ubiquibot]

Property	Value
Wallet	0x24fbA1343132DE969Aeef0B1BD5CaAE1fB102978

[gitcoindev]

I have just queried @BeanieMen to check if the correct wallet was assigned, somehow it is broken for my wallet only..

[BeanieMen]

/query @gitcoindev

[ubiquibot]

Property	Value
Wallet	0x4D0704f400D57Ba93eEa88765C3FcDBD826dCFc4

[BeanieMen]

that wouldnt work because if a open project issue has a assignee, it should be closed in the devpool but after closing the issue in the devpool, that check opened the issue.

will qa after rndquu gives his opinion about this

[BeanieMen]

case 1 was never synced
case 2 this closed because it was unavailable
case 3 this reopened even tho i closed it

[BeanieMen]

@pavlovcik please tell me why you are not reviewing ubiquity/.github#90
its been more than 2 whole weeks

[BeanieMen]

A closed issue is being display in work.ubq.fi

[BeanieMen]

@rndquu the logic should still be the same as the cases where project issue is open is already handled and when it is closed, devpool issue should be closed regardless

[rndquu]

I remember here was a check that if project issue is assigned then don't sync such bounty with devpool. Not sure why this check was removed.

Right now if project issue is open and assigned (and does not exist in devpool) then such issue will be synced while the desired behaviour is to skip already assigned issues in partner projects.

[BeanieMen]

Weird, I remember leaving that check as is

[BeanieMen]

@rndquu can you review this also?

[rndquu]

I remember here was a check that if project issue is assigned then don't sync such bounty with devpool. Not sure why this check was removed.

Right now if project issue is open and assigned (and does not exist in devpool) then such issue will be synced while the desired behaviour is to skip already assigned issues in partner projects.

@BeanieMen Still not implemented

[BeanieMen]

Damn I give up, I can't figure this out