-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add link to the repo for the https://github.github.com/gfm page? #1763
Comments
Stale issue message |
No it isn't: issues need to have been triaged before they can go stale. Instead the bot should be yelling at you, @github, for not even having looked at an issue that's been sitting untriaged for half a year. Don't make a bot flag issues stale that haven't even been looked at yet |
Stale issue message |
never have a bot mark an issue stale until it's been commented on by a project member. This isn't complicated. You're humans, issues are files by humans. |
Stale issue message |
And again. It's almost like no one's looking at this repo, eh @github? |
It would be useful to have a link in the README.md for folks to know where to file issues for the GFM spec (https://github.github.com/gfm) page (and ideally, have that page tell people where it lives so they can file issues about spec incompletion or errors).
I was hoping to find that here because I want to raise the issue that the current spec has too many HTML "start conditions", with several conditions simply being the same thing (condition 7 wholly entails condition 6, warranting a text update.
The text was updated successfully, but these errors were encountered: