/attempt

Available commands

- /start: Assign the origin sender to the issue automatically.
- /stop: Unassign the origin sender from the issue automatically.
- /help: List all available commands.
- /autopay: Toggle automatic payment for the completion of the current issue.
- /query: Comments the users multiplier and address
- /multiplier: Set the bounty payout multiplier for a specific contributor, and provide the reason for why. 
  example usage: "/wallet @user 0.5 'Multiplier reason'"
- /allow: Set access control. (Admin Only)
- /wallet: <WALLET_ADDRESS | ENS_NAME>: Register the hunter's wallet address. 
  ex1: /wallet 0x0000000000000000000000000000000000000000
  ex2: /wallet vitalik.eth

@alankritdabral

/start

Skipping /start because it is disabled on this repo

/wallet

Skipping /wallet because it is disabled on this repo

/start

Skipping /start because it is disabled on this repo

/attempt #870

/start

Skipping /start because it is disabled on this repo

Do you have any updates @AlooDon? If you would like to release the bounty back to the DevPool, please comment /stop
Last activity time: Thu Nov 16 2023 07:49:35 GMT+0000 (Coordinated Universal Time)

/stop

Skipping /stop because it is disabled on this repo

/help

/attempt #884

Hi @TouchstoneTheDev ! Thank you for your contribution. Unfortunately, currently bounties on this particular repository are blocked until a large refactoring pull request is merged. You may want to come back and contribute when this is finalized.

@pavlovcik @gitcoindev can you atleast tell me my pr resolve the issue 🥺

@gitcoindev this issue got closed on dev dir repo ubiquity/devpool-directory#981 (comment)

@gitcoindev this issue got closed on dev dir repo ubiquity/devpool-directory#981 (comment)

perhaps it was already fixed in the refactoring?

I believe it was closed because I removed @ubiquity/ubiquibot from the directory in order to reduce confusion for new people joining. We paused tasks on this repository due to the large refactoring.

@pavlovcik @gitcoindev can you atleast tell me my pr resolve the issue 🥺

The warning has gone so it seems that #896 solves the issue

I believe it was closed because I removed @ubiquity/ubiquibot from the directory in order to reduce confusion for new people joining. We paused tasks on this repository due to the large refactoring.

Exactly, you can always check the reason in CI logs

i think we should give a chance to this contrubitor's PR as it looks like it fix the issue, also not that long to review as per #896 and close this issue as completed perhaps