You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I might be guilty of this in one or two cases myself, this repository generates a lot of issues that aren't an issue with the code but are rather a request for support.
There's a way in Github to add a guidelines file that will appear before anyone can open an issue which would serve as a deterrent for anyone asking for support.
Also, if we have somebody in the community who might be willing to create a Stack Overflow tag for heroku-wp, that would be a better place to direct people to who need support. An update to the readme that leads folks needing support to Stack Overflow would also be in order.
I've seen good projects get overrun with support requests in the Issues leading to the author closing the issues capability and the project dying as a result. I would hate to see that happen here.
The text was updated successfully, but these errors were encountered:
I agree! I could try to write a few lines if it helps.
ryanburnette
changed the title
This repo needs issue guidelines and someplace else to go for support
This project needs issue guidelines and someplace else to go for support
Oct 13, 2019
While I might be guilty of this in one or two cases myself, this repository generates a lot of issues that aren't an issue with the code but are rather a request for support.
There's a way in Github to add a guidelines file that will appear before anyone can open an issue which would serve as a deterrent for anyone asking for support.
Also, if we have somebody in the community who might be willing to create a Stack Overflow tag for heroku-wp, that would be a better place to direct people to who need support. An update to the readme that leads folks needing support to Stack Overflow would also be in order.
I've seen good projects get overrun with support requests in the Issues leading to the author closing the issues capability and the project dying as a result. I would hate to see that happen here.
The text was updated successfully, but these errors were encountered: