Should a label be created for index-generating markup? #11928
Unanswered
electric-coder
asked this question in
Q&A
Replies: 2 comments
-
Seems reasonable, do you have a list of issues / PRs you'd include in the label? A |
Beta Was this translation helpful? Give feedback.
0 replies
-
Give me a few days and I'll start going through the repository to compile a list (aiming at sparing maintainers that research time). I'll add it to this thread as an answer. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Does the community think it might be necessary to create a label in the repository for the index-generating markup?
For example, if we search for the keyword index the current results return 347 open issues and 1,399 closed issues. But most of these are textual coincidences - here's one case where the default
index.rst
was included inconf.py
but nothing in the post is about index-generating markup itself.It's been my experience that cases like these make searching the repository tedious. Historically the repository hasn't kept labels for specific reST directives but perhaps there might be a substantial gain in time not spent searching, for maintainers and users alike, at the costing of creating more labels.
Beta Was this translation helpful? Give feedback.
All reactions