Re: Submitting effective bug reports
@2Yes, you have submitted reports to me in the past, and they've been readable, and provided lots of good information. The report in your post is a great example of a good report IMHO.@3 and @4Yes, I've got templates up and running, and ye
Re: Submitting effective bug reports
Great post! Anywhere a bug can be submitted, this can be a valuable thing to think back on. Thankfully I already do most of these things (I just copied what others were being praised for) but it's still good to be reminded.
URL:
Re: Submitting effective bug reports
#3 and #4 already beat me to it. why not use github templates for bug reports? this post is probably just going to be lost pretty soon.
URL: https://forum.audiogames.net/post/615889/#p615889
--
Audiogames-reflector mailing list
Audiogames
Re: Submitting effective bug reports
@1You know about GitHub templates right? I should probably use one for Synthizer issues, honestly. You just make a .md and put it in a magic spot in your repo.I will just also add that bugs from fellow programmers that come with a "and this is wh
Re: Submitting effective bug reports
Here is an attempt an helping yourself, because you will most likely always get issues like that, but...GitHub issue templates can help at least a bit. Provide a dedicated feature request, bug report, documentation request etc template, and pre-fill it
Re: Submitting effective bug reports
Hello,I think I have reported some bugs to you and I would just like your opinion on my way of doing that in the hopes of improving myselfI most times do the following: 1: describing the situation in which the bug has hapind2: pasting any errors or logs
Submitting effective bug reports
Hi everyone,I'm posting this here, because there seems to be lots of instances lately where people submit bugs in an extremely ineffective manner. I'm not complaining, how are non-developers supposed to know what developers find useful? The an
