It does. All GitHub repositories have issue tracker dBs, and all sorts of other nifty tools.
If you had hovered over the issue link I posted above, you’d have seen that the URL goes direct to a specific issue in the issues dB.
So removing the specific issue number (from the end of the URL) gives you a link to the issue listing:
… to which I’ve added 8 issues in the past week.
GitHub has nifty type marker “labels” that can be created by contributing members and attached to any issue. If you look above in the issue link, you’ll see ThomThom already attached 2 to that issue. (ie, “question” and “enhancement”.)
This is the list of the labels ThomThom (& etc.,) have already created:
Normally this is a documentation error. But we need to be careful as sometimes the API code has changed over the years (perhaps due to the change in embedded Ruby version.)
But, yes, this is the kind of error we are logging, in the GitHub issue tracker for the ruby doc project.
No, this is not a documentation error, this is a API code (engine) error / bug.
This goes into another internal tracker dB, which is not public.
BUT, the docs do have bug note boxes in them, that attempt to notify the coders of bugs and pitfalls. (It is okay to file an issue to add such notes to the API docs.)
There is a separate GitHub project for expanded examples and tutorials:
… which has it’s own issue / feature request list:
… to which I just recently (4 days) posted a new issue for a new class example.