-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix assignment on editing github issue PR description #84
Comments
Looks like the logic to capture the closing keywords also works on edits. I suppose that it should check if it is currently assigned, and if so, to not clobber assignment. |
/start |
Tip
|
I'm not 100% sure, https://github.com/ubiquity-os-marketplace/command-start-stop or https://github.com/ubiquity-os-marketplace/daemon-disqualifier |
@gentlementlegen i am guessing it's command start stop but would be great if you can confirm. |
Yes it is |
Passed the disqualification threshold and no activity is detected, removing assignees: @Sadaf-A. |
I've investigated this, and this happens because there is logic associated to |
Tip
|
|
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Task | 1 | 50 |
Issue | Comment | 2 | 2.46 |
Review | Comment | 1 | 0 |
Conversation Incentives
Comment | Formatting | Relevance | Priority | Reward |
---|---|---|---|---|
Yes it is `command-start-stop`, the disqualifier never a… | 1.59content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 26 wordValue: 0.1 result: 1.59 | 0.8 | 1 | 0.32 |
I've investigated this, and this happens because there is [logic… | 8.57content: content: p: score: 0 elementCount: 1 a: score: 5 elementCount: 1 result: 5 regex: wordCount: 67 wordValue: 0.1 result: 3.57 | 1 | 1 | 2.14 |
Resolves #84QA:- [on editing a pull-request authored by a bo… | 11.5content: content: p: score: 0 elementCount: 5 ul: score: 0 elementCount: 1 li: score: 0.5 elementCount: 3 a: score: 5 elementCount: 2 result: 11.5 regex: wordCount: 35 wordValue: 0 result: 0 | 0.7 | 1 | 0 |
[ 2.405 WXDAI ]
@0x4007
Contributions Overview
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 2 | 2.405 |
Conversation Incentives
Comment | Formatting | Relevance | Priority | Reward |
---|---|---|---|---|
Looks like the logic to capture the closing keywords also works … | 1.85content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 31 wordValue: 0.1 result: 1.85 | 1 | 1 | 1.85 |
@gentlementlegen i am guessing it's command start stop but would… | 1.11content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 17 wordValue: 0.1 result: 1.11 | 0.5 | 1 | 0.555 |
[ 28.82 WXDAI ]
@rndquu
Contributions Overview
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Specification | 1 | 23.59 |
Issue | Comment | 1 | 5.23 |
Conversation Incentives
Comment | Formatting | Relevance | Priority | Reward |
---|---|---|---|---|
There's [this](https://github.com/ubiquity-os/ubiquity-os-plugin… | 23.59content: content: p: score: 0 elementCount: 5 ol: score: 0 elementCount: 1 li: score: 0.5 elementCount: 2 a: score: 5 elementCount: 4 result: 21 regex: wordCount: 46 wordValue: 0.1 result: 2.59 | 1 | 1 | 23.59 |
I'm not 100% sure, https://github.com/ubiquity-os-marketplace/co… | 10.46content: content: p: score: 0 elementCount: 1 a: score: 5 elementCount: 2 result: 10 regex: wordCount: 6 wordValue: 0.1 result: 0.46 | 0.5 | 1 | 5.23 |
There's this issue which was initially assigned to
Keyrxng
.What happened:
ubiquity-os-beta
suddenly assigned me to the issue while the expected behavior was to keepKeyrxng
as the original assigneeP.S. Not sure what's the correct repository for this issue, https://github.com/ubiquity-os-marketplace/command-start-stop or https://github.com/ubiquity-os-marketplace/daemon-disqualifier
The text was updated successfully, but these errors were encountered: