Quuxplusone added inline comments.
================ Comment at: libcxx/docs/index.rst:220 * `libc++abi Homepage <http://libcxxabi.llvm.org/>`_ -* `LLVM Bugzilla <https://bugs.llvm.org/>`_ +* `LLVM Issues <https://github.com/llvm/llvm-project/issues/>`_ * `libcxx-commits Mailing List`_ ---------------- ksyx wrote: > MaskRay wrote: > > Quuxplusone wrote: > > > > > Would https://github.com/llvm/llvm-project/labels/libc++ be better? > > > > Unfortunately "New issue" on that page does not apply the label > > automatically. > Adding parameter like in > <https://github.com/llvm/llvm-project/issues/new?labels=ABI> could be the > most direct way of doing this, given the label exists, so do assignee > (untested)? Besides, the new > [[ > https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms > | Issue Forms ]] feature of GitHub is also a good idea that also unifys what > to fill out in a request and what to automatically do with the issue. Given that you are using the "search for label" URLs in the other places now, I think (for consistency) it //does// make sense to change this one to `https://github.com/llvm/llvm-project/labels/libc++/`. (With or without the trailing slash, but be consistent.) Please do //not// hard-code any links to `https://github.com/llvm/llvm-project/issues/new`-anything; IMHO that makes it far too likely that people (or robots) who click there will end up creating a new spam issue by accident. Someone who's found a bug to report should be taken to the //search page// (to search and see if it's already been filed). Taking them straight to "create a (probably spam) issue" is completely counterproductive. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D116351/new/ https://reviews.llvm.org/D116351 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
