Edit: Nevermind. The document they cite[0] clears it up.
That didn't exactly clear it up for me. Would you mind saying how that clears it up? Does it really mean 1-249 after all?
HN user
[ my public key: https://keybase.io/martinl9; my proof: https://keybase.io/martinl9/sigs/9JibyzdOl6hJAi62QO3TNbAEytOGPxHaTO98at2RDSk ]
Edit: Nevermind. The document they cite[0] clears it up.
That didn't exactly clear it up for me. Would you mind saying how that clears it up? Does it really mean 1-249 after all?
GitHub had issue voting years ago and got rid of it because people hated it.
colinodell posted that before the blog announcement when we only knew about issue_template.md. It was to point out that you can do this with pull requests as well, not that it was case insensitive.
This is the first of many improvements to Issues and Pull Requests that we're working on based on feedback from the community
So there is more to come
Yes. It works on issues too.
Yes. When you subscribe to an issue you show that you are at least interested enough to receive notifications about it.
Do you get many issues that don't use your template because people go to /issues and click the new issue button? When I create an issue with a project, I typically don't a link in readme.md.
It's up to date. It has people who started last week.
This isn't true of GitHub as a whole, and I'm not sure it is true of any part of GitHub. Their team page shows everybody on staff in the order they were hired. Scroll to the bottom and you will see that there is no shortage of white people being hired. https://github.com/about/team