You are viewing a single comment's thread from:
RE: [Bug fix] Incorrect vote value due to incorrect voting power
No problem :) Also, just so you know, you could potentially add bug fixes within the development category instead of in bugs-hunting. I would recommend this when you carry out larger, more complex fixes. I think in this case, with the number of additions made, this is perfect for the bug-hunting category. One to remember for the future :)
Thanks for the additional tip. Yes I actually know dev category and since this is simple as you mentioned, that's why I submitted as bug-hunting :)
Actually, I have a question. What if the bug is already reported but there is no fix and I made a fix. Then is it eligible for bug-hunting category?
In the scenario where a bug has already been reported and you make a fix, this would be a contribution that would fall under the development category. The main purpose of the bug-hunting category is for QA individuals to seek and report issues, however it's always great to see a little more added value to the project through a pull request :)
Thank you for your answer. That's what I expected. By the way, then if it's a simple bug fix, at least it can still be accepted under the dev category? Of course, I don't expect high score, but at least it'd be good to be accepted.
Yes, you can submit smaller bug fixes into development, just explain it well, the reasons it occurred and how you resolved it. As you say, you they may not always be high scores due to the amount of work required, but they're definitely valid contributions in that category.
Thanks! But it says on https://join.utopian.io/guidelines/
"Submissions should include a comprehensible commit history. Projects or updates submitted in a single commit will not be considered for potential reward."
Fortunately, I have a multiple commits, but I still wonder what's the exact rule. You know in some cases, one commit can be very critical.