Bug reports are contributions from people who try to help your project. I don’t go to Github issues to complain - i can do that on socials. I do it as a service for the devs, to make them aware of an issue they may not yet be aware of.
Treating issue reporters like this is just disrespectful of the work they are trying to contribute.
Note that this message only appears AFTER someone has already gone through the work of writing an error report. At that point, just throwing their work into the toilet SUCKS.
It does seem hostile to use a bot deletion and message. The github has an issues tab, it has a submit button. A reasonable user would find their github, and then submit an issue in the normal github bug reporting place on a page that looks like a normal and active issues page only to then be met with the bot deletion message.
Github has the option to disable the issues tab, which they reccomend for projects that do not take bug reports through github. These devs didn’t do that. It appears they use the issues tab for issue tracking internally within the team. The result is a public issues page, that looks just like a normal one that takes user submissions.
The project does say they they only take bug reports on discord on the readme and on the contributors page, both of which are below the fold on browsers. The information is provided in advance of a submission, but not in a way most users will be likely to find it when trying to submit bug reports, as the issues button is directly at the top of the screen.
Their github is indexed on search engines and came up as the second result when searching for “game native” in my test. The discord is not in search results. Users are far more likely to find the github than the discord when searching.
I do hope its unintentional, but it really seems like these devs have set a trap. Reasonable users will find the issues page, spend their time writing a report, only for a bot to autodelete. Its cruel.
Bug reports are contributions from people who try to help your project. I don’t go to Github issues to complain - i can do that on socials. I do it as a service for the devs, to make them aware of an issue they may not yet be aware of.
Treating issue reporters like this is just disrespectful of the work they are trying to contribute.
Note that this message only appears AFTER someone has already gone through the work of writing an error report. At that point, just throwing their work into the toilet SUCKS.
It does seem hostile to use a bot deletion and message. The github has an issues tab, it has a submit button. A reasonable user would find their github, and then submit an issue in the normal github bug reporting place on a page that looks like a normal and active issues page only to then be met with the bot deletion message.
Github has the option to disable the issues tab, which they reccomend for projects that do not take bug reports through github. These devs didn’t do that. It appears they use the issues tab for issue tracking internally within the team. The result is a public issues page, that looks just like a normal one that takes user submissions.
The project does say they they only take bug reports on discord on the readme and on the contributors page, both of which are below the fold on browsers. The information is provided in advance of a submission, but not in a way most users will be likely to find it when trying to submit bug reports, as the issues button is directly at the top of the screen.
Their github is indexed on search engines and came up as the second result when searching for “game native” in my test. The discord is not in search results. Users are far more likely to find the github than the discord when searching.
I do hope its unintentional, but it really seems like these devs have set a trap. Reasonable users will find the issues page, spend their time writing a report, only for a bot to autodelete. Its cruel.
Can you write a blank report to check if they’re doing this, and then edit it if they’re not?
You could, but you’d have to know that some people do this, and it is confusing to maintainers if empty issues keep popping up.
Possibly, or, you can check, the code .github folder for workflows the repo is using.