Open web4er opened 1 year ago
/help
- /start: Assign the origin sender to the issue automatically.
- /stop: Unassign the origin sender from the issue automatically.
- /help: List all available commands.
- /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
/wallet
Please include your wallet or ENS address. usage: /wallet 0x0000000000000000000000000000000000000000
/wallet 0x1F9FCc0E84dc2094499b848AE37Cd6a51db03Ff2
Updated the wallet address for @web4er successfully! Your new address: 0x1F9FCc0E84dc2094499b848AE37Cd6a51db03Ff2
Previously failing functions working on localhost. The image is being generated and sent to the telegram chat.
/start
Deadline | Wed, 02 Aug 2023 18:47:03 UTC |
Registered Wallet | 0x1F9FCc0E84dc2094499b848AE37Cd6a51db03Ff2 |
Payment Multiplier | 0.70 |
Multiplier Reason | testing |
Total Bounty | 13.125 USD |
/wallet 0x0000...0000
if you want to update your registered payment wallet address @user./stop
You have been unassigned from the bounty @web4er
disable-analytics: true
/allow set-multiplier @web4er true
Updated access for @web4er successfully! Access: multiplier for "web4er/ubiquibot"
/multiplier 0.7 @web4er "testing"
Successfully changed the payout multiplier for @web4er to 0.7. The reason provided is "testing ".
I realized that it was not processing events for analytics of non-org users. Also fixed that. Here are the results.
There is not much to show here related to local development issues. However, we will test things fixed after fixing local development issue which were broken.
We will run random commands in this QA. Some commands will be written invalid on purpose to test the correct response.
First, tests will be performed in a single
yarn build && yarn start
withdisable-analytics": false
. The reason is testing previously failing analytics functions on localhost:After this, some tests will be performed with
disable-analytics": true