@Gptaqbc commented on GitHub (Nov 9, 2019):
This isn't true... or at least can't be replicated.
If this is talking about the fact that you have to click the…
@Gptaqbc commented on GitHub (Oct 29, 2019):
Oh yeah, that’s sure. Issues have to stay open until completely resolved. I just asked to merge 2 issues together…
@RedSparr0w commented on GitHub (Oct 29, 2019):
But they are separate problems, they may be similar/have a similar fix, but they are quite different problems.
@Gptaqbc commented on GitHub (Oct 29, 2019):
What should I do then? I dont want someone working on that because it’s fixed on my side.
@RedSparr0w commented on GitHub (Oct 29, 2019):
Just comment here, and put it on your PR when you create it. Basically the same thing you would do on the other…
@dginovker commented on GitHub (Oct 29, 2019):
Closed for #107
@RedSparr0w commented on GitHub (Oct 29, 2019):
You don't need to be assigned an issue to work on it 😄 When you create the PR what you would usually do is…
@Gptaqbc commented on GitHub (Oct 29, 2019):
It’s not that I want or need to be assigned. It’s that I dont want other contributors to start working on it while…
@RedSparr0w commented on GitHub (Oct 29, 2019):
Yeah, once the comment is there other people should notice someone is already working on it, just saying better…
@michae107 commented on GitHub (Oct 26, 2019):
Sorry I didn't see it in the issues, remove this if necessary. I'll work on fixing this one for my first pull request.
@Gptaqbc commented on GitHub (Oct 26, 2019):
It only happens if the stack was sold using the sell all option IIRC
@DPSCryptic commented on GitHub (Oct 26, 2019):
indeed, its not in the issues, thanks for adding it
@RedSparr0w commented on GitHub (Oct 26, 2019):
seems to happen with any amount sold.
@Gptaqbc commented on GitHub (Oct 29, 2019):
Is it possible to merge that issue with the #107? I got this fixed in my work in progress.