Task Matchmaking #7
Comments
|
@0x4007 So to sum up:
So, to find the who completed the task. Should |
|
First use assignees and fallback to pull author since many organizations are not as strict about assignment. The plan is to separately build a scraper basically so when a new person joins our DevPool we can scrape all the public data on their profile to know what types of projects they completed. |
Is scraper a part of this ticket ? If so, could you add more details about it to the issue spec. So, right now Also, |
Different project. Can make the spec later. I imagine we could ask them to install UbiquityOS and then we can read all the issues from their private repositories.
Yes
Multiple comments isn't preferred. If we can edit the single comment it would look better. For issues similarity we can also consider editing the specification and adding a footer regarding similarities.
This can be handled in a separate task |
|
/start |
Tip
|
|
I attempted to address a few issues, but I’m wondering if the kernel supports Currently, when an issue is assigned, the payload doesn’t update. Is there another plugin that handles this update? If I add webhook support for |
We do want to decrease coupling but at this point I am leaning towards stacking tech debt so that we can ship more capabilities faster. We had quite a lull in the last couple of months and I want to speed things along. So do what you think is faster to ship and we can clean tech debt later. You are also free to create a separate plugin if you think that makes sense! Perhaps @gentlementlegen can provide some advice on how to chain outputs together? |
|
When multiple plugins are specified under a |
Are you using your own GitHub App? Have you correctly set the permissions? If you are using our kernel, the official instance, it definitely relays label events. |
I fixed that, it was |
|
| View | Contribution | Count | Reward |
|---|---|---|---|
| Issue | Task | 1 | 600 |
| Issue | Comment | 4 | 12.818 |
| Review | Comment | 8 | 0 |
Conversation Incentives
| Comment | Formatting | Relevance | Reward |
|---|---|---|---|
@0x4007 So to sum up:- `Issues` Database, would have t… | 4.13content:
p:
symbols:
\b\w+\b:
count: 66
multiplier: 0.1
score: 1
ul:
symbols:
\b\w+\b:
count: 1
multiplier: 0.1
score: 1
li:
symbols:
\b\w+\b:
count: 2
multiplier: 0.1
score: 1
code:
symbols:
\b\w+\b:
count: 4
multiplier: 0.1
score: 1
multiplier: 1
| 0.8 | 3.304 |
Is scraper a part of this ticket ? If so, could you add more det… | 6.54content:
p:
symbols:
\b\w+\b:
count: 96
multiplier: 0.1
score: 1
code:
symbols:
\b\w+\b:
count: 28
multiplier: 0.1
score: 1
multiplier: 1
| 0.9 | 5.886 |
I attempted to address a few issues, but I’m wondering if the ke… | 5.75content:
p:
symbols:
\b\w+\b:
count: 98
multiplier: 0.1
score: 1
code:
symbols:
\b\w+\b:
count: 12
multiplier: 0.1
score: 1
multiplier: 1
| 0.6 | 3.45 |
I fixed that, it was `issues.labled`, I was using someth… | 0.89content:
p:
symbols:
\b\w+\b:
count: 10
multiplier: 0.1
score: 1
code:
symbols:
\b\w+\b:
count: 2
multiplier: 0.1
score: 1
multiplier: 1
| 0.2 | 0.178 |
Resolves #7 - Adds a `issue` matching option. - Wo… | 0content:
p:
symbols:
\b\w+\b:
count: 20
multiplier: 0
score: 1
ul:
symbols:
\b\w+\b:
count: 1
multiplier: 0
score: 1
li:
symbols:
\b\w+\b:
count: 3
multiplier: 0
score: 1
code:
symbols:
\b\w+\b:
count: 7
multiplier: 0
score: 1
multiplier: 0
| 0.8 | - |
Adding the space, somehow breaks it. I tried without space, it d… | 0content:
p:
symbols:
\b\w+\b:
count: 16
multiplier: 0.2
score: 1
multiplier: 0
| 0.5 | - |
It works well both with and without the space, based on my tests. | 0content:
p:
symbols:
\b\w+\b:
count: 13
multiplier: 0.2
score: 1
multiplier: 0
| 0.4 | - |
Example issue:[New Issue](https://github.com/sshivaditya2019/t… | 0content:
p:
symbols:
\b\w+\b:
count: 42
multiplier: 0.2
score: 1
a:
symbols:
\b\w+\b:
count: 4
multiplier: 0.2
score: 1
code:
symbols:
\b\w+\b:
count: 8
multiplier: 0.2
score: 1
multiplier: 0
| 0.7 | - |
If some is assigned an issue that particular issue's payload is … | 0content:
p:
symbols:
\b\w+\b:
count: 60
multiplier: 0.2
score: 1
multiplier: 0
| 0.6 | - |
Fixed, Now, its using graphQL for query, listens only for `i… | 0content:
p:
symbols:
\b\w+\b:
count: 15
multiplier: 0.2
score: 1
code:
symbols:
\b\w+\b:
count: 6
multiplier: 0.2
score: 1
a:
symbols:
\b\w+\b:
count: 4
multiplier: 0.2
score: 1
multiplier: 0
| 0.9 | - |
Updated the comment structure, the comments should start with &#… | 0content:
p:
symbols:
\b\w+\b:
count: 25
multiplier: 0.2
score: 1
code:
symbols:
\b\w+\b:
count: 1
multiplier: 0.2
score: 1
multiplier: 0
| 0.9 | - |
Its working, you can check the updated comment in the ([Old Issu… | 0content:
p:
symbols:
\b\w+\b:
count: 10
multiplier: 0.2
score: 1
a:
symbols:
\b\w+\b:
count: 2
multiplier: 0.2
score: 1
multiplier: 0
| 0.6 | - |
[ 67.76 WXDAI ]
@0x4007
Contributions Overview
| View | Contribution | Count | Reward |
|---|---|---|---|
| Issue | Specification | 1 | 51.76 |
| Issue | Comment | 4 | 14.649 |
| Review | Comment | 7 | 1.351 |
Conversation Incentives
| Comment | Formatting | Relevance | Reward |
|---|---|---|---|
When a new task is posted to our network, UbiquityOS should reco… | 51.76content:
p:
symbols:
\b\w+\b:
count: 198
multiplier: 0.1
score: 1
ul:
symbols:
\b\w+\b:
count: 3
multiplier: 0.1
score: 0
li:
symbols:
\b\w+\b:
count: 27
multiplier: 0.1
score: 1
code:
symbols:
\b\w+\b:
count: 21
multiplier: 0.1
score: 5
pre:
symbols:
\b\w+\b:
count: 1
multiplier: 0.1
score: 0
hr:
symbols:
\b\w+\b:
count: 1
multiplier: 0.1
score: 0
multiplier: 3
| 1 | 51.76 |
First use assignees and fallback to pull author since many organ… | 5.75content:
p:
symbols:
\b\w+\b:
count: 52
multiplier: 0.2
score: 1
multiplier: 1
| 0.4 | 2.3 |
Different project. Can make the spec later. I imagine we could a… | 7.31content:
p:
symbols:
\b\w+\b:
count: 69
multiplier: 0.2
score: 1
multiplier: 1
| 0.5 | 3.655 |
`issues.label_added` is certainly supported. That is how… | 11.01content:
p:
symbols:
\b\w+\b:
count: 98
multiplier: 0.2
score: 1
code:
symbols:
\b\w+\b:
count: 4
multiplier: 0.2
score: 1
a:
symbols:
\b\w+\b:
count: 3
multiplier: 0.2
score: 1
multiplier: 1
| 0.7 | 7.707 |
Are you using your own GitHub App? Have you correctly set the pe… | 3.29content:
p:
symbols:
\b\w+\b:
count: 27
multiplier: 0.2
score: 1
multiplier: 1
| 0.3 | 0.987 |
Did you test this? The syntax doesn't look correct. Pretty sure … | 0.32content:
p:
symbols:
\b\w+\b:
count: 20
multiplier: 0.1
score: 1
multiplier: 0.25
| 0.7 | 0.224 |
```suggestionconst commentLines: string[] = [">… | 0.22content:
pre:
symbols:
\b\w+\b:
count: 1
multiplier: 0.1
score: 0
code:
symbols:
\b\w+\b:
count: 13
multiplier: 0.1
score: 1
multiplier: 0.25
| 0.8 | 0.176 |
```suggestioncommentLines.push(`> ### [$… | 0.15content:
pre:
symbols:
\b\w+\b:
count: 1
multiplier: 0.1
score: 0
code:
symbols:
\b\w+\b:
count: 8
multiplier: 0.1
score: 1
multiplier: 0.25
| 0.8 | 0.12 |
I don't understand what you mean by this.Only closed as comple… | 0.7content:
p:
symbols:
\b\w+\b:
count: 50
multiplier: 0.1
score: 1
multiplier: 0.25
| 0.6 | 0.42 |
I'm sorry but I have little context on the "payload object" I ha… | 0.55content:
p:
symbols:
\b\w+\b:
count: 38
multiplier: 0.1
score: 1
multiplier: 0.25
| 0.3 | 0.165 |
QA looking good. Please check my comment under "old issue" regar… | 0.32content:
p:
symbols:
\b\w+\b:
count: 20
multiplier: 0.1
score: 1
multiplier: 0.25
| 0.7 | 0.224 |
@gentlementlegen can you install this plugin | 0.11content:
p:
symbols:
\b\w+\b:
count: 6
multiplier: 0.1
score: 1
multiplier: 0.25
| 0.2 | 0.022 |
[ 0 WXDAI ]
@gentlementlegen
Contributions Overview
| View | Contribution | Count | Reward |
|---|---|---|---|
| Issue | Comment | 1 | 0 |
Conversation Incentives
| Comment | Formatting | Relevance | Reward |
|---|---|---|---|
When multiple plugins are specified under a `uses` key, … | 0content:
p:
symbols:
\b\w+\b:
count: 20
multiplier: 0.1
score: 1
code:
symbols:
\b\w+\b:
count: 1
multiplier: 0.1
score: 1
multiplier: 1
| - | - |
When a new task is posted to our network, UbiquityOS should recommend qualified contributors.
issues.label_addedissues.createdissues.editedwww.prefix on the github href so that it does not register as a "link back" on the GitHub UI over on their issue.For example it should look something like:
Eventually this may be configurable to be network wide (global) organization wide, or repository wide. But for this first version, we will do network wide.
Another configuration of this idea could be to recommend the contributor in the organization with the highest match, even if it doesn't hit the threshold. If within the organization, perhaps tagging is appropriate. Perhaps it makes sense to handle this in a separate task.
The text was updated successfully, but these errors were encountered: