Closed 0x4007 closed 7 months ago
/help
Command | Description | Example |
---|---|---|
/start |
Assign yourself to the issue. | /start |
/stop |
Unassign yourself from the issue. | /stop |
/help |
List all available commands. | /help |
/query |
Returns the user's wallet, access, and multiplier information. | /query @user |
/ask |
Ask a context aware question. | /ask is x or y the best approach? |
/multiplier |
Set the task payout multiplier for a specific contributor, and provide a reason for why. | /multiplier @user 0.5 "multiplier reason" |
/labels |
Set access control, for admins only. | /labels @user priority time price |
/authorize |
Approve a label change, for admins only. | /authorize |
/wallet |
Register your wallet address for payments. | /wallet ubq.eth |
/start
Deadline | Sat, Feb 24, 1:30 AM UTC |
Registered Wallet | 0xf76F1ACB66020f893c95371f740549F312DEA3f1 |
/wallet 0x0000...0000
if you want to update your registered payment wallet address./help
Command | Description | Example |
---|---|---|
/start |
Assign yourself to the issue. | /start |
/stop |
Unassign yourself from the issue. | /stop |
/help |
List all available commands. | /help |
/query |
Returns the user's wallet, access, and multiplier information. | /query @user |
/ask |
Ask a context aware question. | /ask is x or y the best approach? |
/multiplier |
Set the task payout multiplier for a specific contributor, and provide a reason for why. | /multiplier @user 0.5 "multiplier reason" |
/labels |
Set access control, for admins only. | /labels @user priority time price |
/authorize |
Approve a label change, for admins only. | /authorize |
/wallet |
Register your wallet address for payments. | /wallet ubq.eth |
/start
! Skipping '/start' because the issue is already assigned.
hey @pavlovcik , since the task was of <2hours, and 13 hours have passed from the assignee. Can i take this up?
We allow for a few days grace period for deliverables to be turned around.
@pavlovcik ready to review.. added QA
+ Evaluating results. Please wait...
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Specification | 1 | 19.4 |
Issue | Comment | 1 | 2.8 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
It would be great for marketing purposes to tally up the total a... | 19.4hr: count: 1 score: "1" words: 0 | 1 | 19.4 |
We allow for a few days grace period for deliverables to be turn... | 2.8 | 0.13 | 2.8 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Task | 1 | 100 |
Issue | Comment | 1 | 0 |
Issue | Comment | 1 | 0.6 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
@pavlovcik ready to review.. added QA... | - | 0.02 | - |
@pavlovcik ready to review.. added QA... | 0.6 | 0.02 | 0.6 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 1 | 2.1 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
hey @pavlovcik , since the task was of <2hours, and 13 hours hav... | 2.1 | 0.19 | 2.1 |
@pavlovcik I just noticed an issue, sync issues run every time there is a push to development.. because there is a push to update rewards, its stuck in an infinite loop
I think that can be fixed by ignoring the workflow if its the reward file been pushed
Sure it's a good idea that you open a pull asap!
[ 22.2 WXDAI ]
@pavlovcik
Contributions Overview
View Contribution Count Reward Issue Specification 1 19.4 Issue Comment 1 2.8 Conversation Incentives
Comment Formatting Relevance Reward It would be great for marketing purposes to tally up the total a...
19.4
hr: count: 1 score: "1" words: 01 19.4 We allow for a few days grace period for deliverables to be turn...
2.8 0.13 2.8
[ 100.6 WXDAI ]
@devpanther
Contributions Overview
View Contribution Count Reward Issue Task 1 100 Issue Comment 1 0 Issue Comment 1 0.6 Conversation Incentives
Comment Formatting Relevance Reward @pavlovcik ready to review.. added QA...
- 0.02 - @pavlovcik ready to review.. added QA...
0.6 0.02 0.6
[ 2.1 WXDAI ]
@guha-rahul
Contributions Overview
View Contribution Count Reward Issue Comment 1 2.1 Conversation Incentives
Comment Formatting Relevance Reward hey @pavlovcik , since the task was of <2hours, and 13 hours hav...
2.1 0.19 2.1
Very weird that it didn't read from the pull request.
@pavlovcik I have an hotfix ready
It would be great for marketing purposes to tally up the total amount of rewards we have available at any given moment by looking up all of the open issues and summing the prices.
I'm not sure where is the best place to write this information (perhaps just a simple text file in the repository somewhere) but it is important that we have access to this number from our home page at ubq.fi via a simple fetch request.
Inspired by https://x.com/ljxie/status/1753615859623321842?s=46&t=bdMjuqzO5LYxLUsloRROxQ