Update Bug report URL to Github Issues

[ChuanqiXu]

Summary

I found that although we moved to Github Issues. The bug report message refers to Bugzilla still. This patch tries to update these URLs. I left FIXME for places where I am not sure how to do wording.

[MaskRay]

llvm/docs/DeveloperPolicy.rst

64

You can drop this and let others fix this paragraph.

[asl]

Thanks for doing this! I added few notes on the way.

clang/www/c_status.html

76

The component got mapped to dedicated label in GitHub. So, it will be great to get rid of bugzilla-centric definition and switch to GitHub terms

clang/www/cxx_status.html

81

Ditto. Also, there are separate labels for C++11 / 14 / 20 / 23. It might make sense to mention them here

clang/www/get_involved.html

69

I think it would make sense to get rid of bz here. For new contributors everything should be GitHub-centric

libcxx/docs/index.rst

220

I'd remove bugzilla here

libunwind/docs/index.rst

101

And here

llvm/docs/HowToReleaseLLVM.rst

280

This is for @tstellar :)

[ChuanqiXu]

Address comments.

[asl]

Will you please check the comments and reword everything using proper terminology and new things we're having on GitHub?

clang/www/c_status.html

76

As I said – there is no "Clang C component" in github. We need to reword everything in terms of labels and mention correct label here.

clang/www/cxx_status.html

81

See above

[ChuanqiXu]

Address comments.

[ChuanqiXu]

clang/www/c_status.html

76

My bad. I didn't realize "Clang C Component" is specific to bugzilla.

clang/www/cxx_status.html

81

BTW, I checked that there isn't c++23 labels now.

[ldionne]

Libc++ and libunwind changes LGTM

[• Quuxplusone]

Tweaked English wording throughout. LGTM with all these modifications made.

Orthogonally, it does occur to me that one might save a lot of this churn (and also the next time the bug tracker moves, e.g. if we go from GitHub to something else) by simply HTTP-redirecting the front page of https://bugs.llvm.org/ to https://github.com/llvm/llvm-project/issues/ . Then we'd have a stable URL https://bugs.llvm.org/ for "reporting LLVM bugs, forever," and we could just use that stable URL everywhere. But OTOH, that's a devops task, whereas updating a bunch of documentation in the repo is easy. :)

clang-tools-extra/docs/clang-doc.rst

15

Please leave the English wording as "the LLVM bugtracker" (or "the LLVM bug tracker" — really it should be two words). There is no such noun in English as "an Issues," which means that the reader won't have any idea what you're talking about here unless they click on the link to see where it goes.

clang/www/c_status.html

75–78

clang/www/cxx_status.html

82–83

(I think , "C++17", "C++20", "C++23" would just be redundant/noise here, and would imply a thankless task for someone to go update this list every 3 years. Better to just cap it at one or two labels. The reader can be trusted to figure out that C++20 issues should be labeled with C++20.)

clang/www/get_involved.html

68–69

clang/www/get_started.html

22

libcxx/docs/index.rst

220–221

libunwind/docs/index.rst

101–102

lld/docs/_templates/indexsidebar.html

3–4

[MaskRay]

@jhenderson

libunwind/docs/index.rst

101–102

https://github.com/llvm/llvm-project/labels/libunwind

lld/docs/_templates/indexsidebar.html

3–4

While here, mention the labels: lld:COFF lld:ELF lld:MachO lld:wasm.

llvm/docs/CommandGuide/llvm-objdump.rst

400

https://github.com/llvm/llvm-project/labels/tools:llvm-objdump

llvm/docs/CommandGuide/llvm-size.rst

194

https://github.com/llvm/llvm-project/labels/tools:llvm-size

llvm/docs/CommandGuide/llvm-strings.rst

126

https://github.com/llvm/llvm-project/labels/tools:llvm-strings

llvm/docs/CommandGuide/llvm-strip.rst

197

https://github.com/llvm/llvm-project/labels/tools:llvm-objcopy%2Fstrip

[MaskRay]

libcxx/docs/index.rst

220–221

Would https://github.com/llvm/llvm-project/labels/libc++ be better?

Unfortunately "New issue" on that page does not apply the label automatically.

[ChuanqiXu]

Address comments.

[ChuanqiXu]

clang/www/c_status.html

75–78

I use the lower-case 'c' to keep consistent with GitHub labels.

clang/www/cxx_status.html

82–83

I use the lower-case 'c' to keep consistent with GitHub labels.

lld/docs/_templates/indexsidebar.html

3–4

I found label lld would cover the sub-labels.

[MaskRay]

llvm/docs/CommandGuide/llvm-objcopy.rst

539

https://github.com/llvm/llvm-project/labels/tools:llvm-objcopy/strip

You need to check whether other tools have dedicated labels.

[ChuanqiXu]

Address comments.

[ChuanqiXu]

llvm/docs/CommandGuide/llvm-objcopy.rst

539

Thanks for reminding me this. I have found there is a label for lldb too. But I don't find labels for other tools.

[xbolva00]

llvm/utils/gn/secondary/clang/include/clang/Config/BUILD.gn

10

This url should redirect to github - who maintains llvm website?

[MaskRay]

lld/docs/_templates/indexsidebar.html

3–4

You can drop changes to this file. I updated it separately.

[ChuanqiXu]

Drop the change in lld.

[ChuanqiXu]

llvm/utils/gn/secondary/clang/include/clang/Config/BUILD.gn

10

It redirects to the issue list correctly in my environment. Or you mean the url shouldn't refer to GitHub issues? I am a little bit confused.

[ksyx]

libcxx/docs/index.rst

220–221

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
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.

[• Quuxplusone]

libcxx/docs/index.rst

220–221

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.

[MaskRay]

libcxx/docs/index.rst

220–221

It's always important to check existing issues before filing a new one. I agree /new should be avoided.

[ChuanqiXu]

@asl hi, do you feel good with this revision?

[jhenderson]

llvm/docs/CommandGuide/llvm-install-name-tool.rst

79

I believe llvm-install-name-tool is a variation of llvm-objcopy, so should probably reference the llvm-objcopy URL.

llvm/docs/CommandGuide/llvm-otool.rst

135

I believe llvm-otool is a variation of llvm-objdump, so should reference the llvm-objdump URL.

[ChuanqiXu]

Address comments.

[jhenderson]

LGTM, from my point of view.

[ChuanqiXu]

It looks like @asl isn't here and many experienced guys accepted this. So I think it might should be good to commit this one.

clang-tools-extra/docs/clang-doc.rst

 ===================
 Clang-Doc
 ===================
 
 .. contents::
 
 .. toctree::
    :maxdepth: 1
 
 :program:`clang-doc` is a tool for generating C and C++ documentation from
 source code and comments.
 
 The tool is in a very early development stage, so you might encounter bugs and
 crashes. Submitting reports with information about how to reproduce the issue
-to `the LLVM bugtracker <https://bugs.llvm.org/>`_ will definitely help the
+to `the LLVM Issues <https://github.com/llvm/llvm-project/issues/>`_ will definitely help the
 project. If you have any ideas or suggestions, please to put a feature request
 there.
 
 Use
 ===
 
 :program:`clang-doc` is a `LibTooling
 <https://clang.llvm.org/docs/LibTooling.html>`_-based tool, and so requires a

clang/docs/CommandGuide/clang.rst

.. envvar:: MACOSX_DEPLOYMENT_TARGET
 
   If :option:`-mmacosx-version-min` is unspecified, the default deployment
   target is read from this environment variable. This option only affects
   Darwin targets.
 
 BUGS
 ----
 
-To report bugs, please visit <https://bugs.llvm.org/>.  Most bug reports should
+To report bugs, please visit <https://github.com/llvm/llvm-project/issues/>.  Most bug reports should
 include preprocessed source files (use the :option:`-E` option) and the full
 output of the compiler, along with information to reproduce.
 
 SEE ALSO
 --------
 
 :manpage:`as(1)`, :manpage:`ld(1)`

clang/www/c_status.html

 investigation. Any proposal whose status in Clang is currently unknown
 will be marked in <span class="unknown">magenta</span>.</p>
 
 <p>The Clang community is continually striving to improve C standards
 compliance between releases. We implement the resolution for defect
 reports, but we do not currently track our DR status (help with
 tracking DR status is appreciated).</p>
 
-<p>The <a href="https://bugs.llvm.org/">LLVM bug tracker</a> contains a
-Clang C component that tracks known bugs with Clang's language
+<p>The <a href="https://bugs.llvm.org/">LLVM bug tracker</a> and 
+<a href="https://github.com/llvm/llvm-project/issues/">LLVM Issues</a> contain
+a Clang C component that tracks known bugs with Clang's language
 conformance.</p>
 
 <h2 id="c89">C89 implementation status</h2>
 
 <p>Clang implements all of the ISO 9899:1990 (C89) standard.</p>
 <p>You can use Clang in C89 mode with the <code>-std=c89</code> or <code>-std=c90</code> options.</p>
 
 <h2 id="c99">C99 implementation status</h2>
 

clang/www/cxx_status.html

 compliance between releases by submitting and tracking <a
 href="cxx_dr_status.html">C++ Defect Reports</a> and implementing resolutions
 as they become available.</p>
 
 <p>Experimental work is also under way to implement <a href="#ts">C++ Technical
 Specifications</a> that will help drive the future of the C++ programming
 language.</p>
 
-<p>The <a href="https://bugs.llvm.org/">LLVM bug tracker</a> contains Clang
-C++ components that track known bugs with Clang's language conformance in
+<p>The <a href="https://bugs.llvm.org/">LLVM bug tracker</a> and 
+<a href="https://github.com/llvm/llvm-project/issues/">LLVM Issues</a> contain
+Clang C++ components that track known bugs with Clang's language conformance in
 each language mode.</p>
 
 <h2 id="cxx98">C++98 implementation status</h2>
 
 <p>Clang implements all of the ISO C++ 1998 standard
   (including the defects addressed in the ISO C++ 2003 standard)
   except for <tt>export</tt> (which was removed in C++11).
 
 <h2 id="cxx11">C++11 implementation status</h2>
 

clang/www/get_involved.html

 discussions or follow the list development on the web if you prefer.</p>
 
 <p>You can also follow the <a href="http://planet.clang.org/">Planet Clang</a>
 community news feed which offers a window into the world, work and lives of
 Clang developers, contributors and the standards they implement.</p>
 
 <p>If you're looking for something to work on, check out our <a
 href="OpenProjects.html">Open Projects</a> page or look through the <a
-href="https://bugs.llvm.org/">Bugzilla bug database</a>.</p>
+href="https://bugs.llvm.org/">Bugzilla bug database</a> or <a
+href="https://github.com/llvm/llvm-project/issues/">LLVM Issues</a>.</p>
 
 <h2 id="criteria">Contributing Extensions to Clang</h2>
 
 <p>Clang is designed to support experimentation,
 allowing programmers to easily extend the compiler to support great
 new language features and tools. At some point, the authors of these
 extensions may propose that the extensions become a part of Clang
 itself, to benefit the whole Clang community. However, extensions

clang/www/get_started.html

 <div id="content">
 
 <h1>Getting Started: Building and Running Clang</h1>
 
 <p>This page gives you the shortest path to checking out Clang and demos a few
 options.  This should get you up and running with the minimum of muss and fuss.
 If you like what you see, please consider <a href="get_involved.html">getting
 involved</a> with the Clang community.  If you run into problems, please file
-bugs in <a href="https://bugs.llvm.org/">LLVM Bugzilla</a>.</p>
+bugs in <a href="https://github.com/llvm/llvm-project/issues">LLVM Issues</a>.</p>
 
 <h2 id="download">Release Clang Versions</h2>
 
 <p>Clang is released as part of regular LLVM releases. You can download the release versions from <a href="https://llvm.org/releases/">https://llvm.org/releases/</a>.</p>
 <p>Clang is also provided in all major BSD or GNU/Linux distributions as part of their respective packaging systems. From Xcode 4.2, Clang is the default compiler for Mac OS X.</p>
 
 <h2 id="build">Building Clang and Working with the Code</h2>
 

clang/www/menu.html.incl

<div class="submenu">
     <a href="/docs/Tooling.html">Writing Clang Tools</a>
   </div>
 
   <div class="submenu">
     <label>Communication</label>
     <a href="http://lists.llvm.org/mailman/listinfo/cfe-users">cfe-users List</a>
     <a href="http://lists.llvm.org/mailman/listinfo/cfe-dev">cfe-dev List</a>
     <a href="http://lists.llvm.org/mailman/listinfo/cfe-commits">cfe-commits List</a>
-    <a href="https://bugs.llvm.org/">Bug Reports</a>
+    <a href="https://github.com/llvm/llvm-project/issues">Bug Reports</a>
     <a href="http://planet.clang.org/">Planet Clang</a>
     <a href="irc://irc.oftc.net/llvm">IRC: irc.oftc.net#llvm</a>
   </div>
 
   <div class="submenu">
     <label>The Code</label>
     <a href="/get_started.html#build">Check Out Sources</a>
     <a href="https://github.com/llvm/llvm-project/tree/main/clang/">Browse Sources</a>

libcxx/docs/index.rst

 Send discussions and questions to the
 `libcxx-dev mailing list <http://lists.llvm.org/mailman/listinfo/libcxx-dev>`_.
 
 
 Quick Links
 ===========
 * `LLVM Homepage <https://llvm.org/>`_
 * `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`_
 * `libcxx-dev Mailing List`_
 * `Browse libc++ Sources <https://github.com/llvm/llvm-project/tree/main/libcxx/>`_

libunwind/docs/index.rst

 Send discussions and questions to the
 `cfe-dev mailing list <http://lists.llvm.org/mailman/listinfo/cfe-dev>`_.
 Please include [libunwind] in the subject.
 
 
 Quick Links
 ===========
 * `LLVM Homepage <https://llvm.org/>`_
 * `LLVM Bugzilla <https://bugs.llvm.org/>`_
+* `LLVM Issues <https://github.com/llvm/llvm-project/issues/>`_
 * `cfe-commits Mailing List`_
 * `cfe-dev Mailing List`_
 * `Browse libunwind Sources <https://github.com/llvm/llvm-project/blob/main/libunwind/>`_

lld/docs/_templates/indexsidebar.html

 <h3>Bugs</h3>
 
 <p>lld bugs should be reported at the
-  LLVM <a href="https://bugs.llvm.org/">Bugzilla</a>.</p>
+  LLVM <a href="https://github.com/llvm/llvm-project/issues/">Issues</a>.</p>

lldb/docs/index.rst

 
 .. toctree::
    :hidden:
    :maxdepth: 1
    :caption: External Links
 
    Source Code <https://github.com/llvm/llvm-project>
    Code Reviews <https://reviews.llvm.org>
-   Bug Reports <https://bugs.llvm.org/>
+   Bug Reports <https://github.com/llvm/llvm-project/issues/>

llvm/CMakeLists.txt

 
 include(VersionFromVCS)
 
 option(LLVM_APPEND_VC_REV
   "Embed the version control system revision in LLVM" ON)
 
 set(PACKAGE_NAME LLVM)
 set(PACKAGE_STRING "${PACKAGE_NAME} ${PACKAGE_VERSION}")
-set(PACKAGE_BUGREPORT "https://bugs.llvm.org/")
+set(PACKAGE_BUGREPORT "https://github.com/llvm/llvm-project/issues/")
 
 set(BUG_REPORT_URL "${PACKAGE_BUGREPORT}" CACHE STRING
   "Default URL where bug reports are to be submitted.")
 
 # Configure CPack.
 set(CPACK_PACKAGE_INSTALL_DIRECTORY "LLVM")
 set(CPACK_PACKAGE_VENDOR "LLVM")
 set(CPACK_PACKAGE_VERSION_MAJOR ${LLVM_VERSION_MAJOR})

llvm/docs/CommandGuide/llvm-install-name-tool.rst

 -----------
 
 :program:`llvm-install-name-tool` exits with a non-zero exit code if there is an error.
 Otherwise, it exits with code 0.
 
 BUGS
 ----
 
-To report bugs, please visit <https://bugs.llvm.org/>.
+To report bugs, please visit <https://github.com/llvm/llvm-project/issues/>.
 
 SEE ALSO
 --------
 
 :manpage:`llvm-objcopy(1)`

llvm/docs/CommandGuide/llvm-libtool-darwin.rst

 -----------
 
 :program:`llvm-libtool-darwin` exits with a non-zero exit code if there is an error.
 Otherwise, it exits with code 0.
 
 BUGS
 ----
 
-To report bugs, please visit <https://bugs.llvm.org/>.
+To report bugs, please visit <https://github.com/llvm/llvm-project/issues/>.
 
 SEE ALSO
 --------
 
 :manpage:`llvm-ar(1)`

llvm/docs/CommandGuide/llvm-lipo.rst

.. option:: -segalign
   Additional flag that can be specified with create and replace.
   The segalign flag is followed by an architecture type, and an alignment.
   The alignment is a hexadecimal number that is a power of 2.
   Output a file in which the slice with the specified architecture has the specified alignment.
 
 BUGS
 ----
 
-To report bugs, please visit <https://bugs.llvm.org/>.
+To report bugs, please visit <https://github.com/llvm/llvm-project/issues/>.

llvm/docs/CommandGuide/llvm-objcopy.rst

 -----------
 
 :program:`llvm-objcopy` exits with a non-zero exit code if there is an error.
 Otherwise, it exits with code 0.
 
 BUGS
 ----
 
-To report bugs, please visit <https://bugs.llvm.org/>.
+To report bugs, please visit <https://github.com/llvm/llvm-project/issues/>.
 
 There is a known issue with :option:`--input-target` and :option:`--target`
 causing only ``binary`` and ``ihex`` formats to have any effect. Other values
 will be ignored and :program:`llvm-objcopy` will attempt to guess the input
 format.
 
 SEE ALSO
 --------
 
 :manpage:`llvm-strip(1)`

llvm/docs/CommandGuide/llvm-objdump.rst

 
 .. option:: --symbol-description
 
   Add symbol description to disassembly output.
 
 BUGS
 ----
 
-To report bugs, please visit <https://bugs.llvm.org/>.
+To report bugs, please visit <https://github.com/llvm/llvm-project/issues/>.
 
 SEE ALSO
 --------
 
 :manpage:`llvm-nm(1)`, :manpage:`llvm-otool(1)`, :manpage:`llvm-readelf(1)`,
 :manpage:`llvm-readobj(1)`

llvm/docs/CommandGuide/llvm-otool.rst

 -----------
 
 :program:`llvm-otool` exits with a non-zero exit code if there is an error.
 Otherwise, it exits with code 0.
 
 BUGS
 ----
 
-To report bugs, please visit <https://bugs.llvm.org/>.
+To report bugs, please visit <https://github.com/llvm/llvm-project/issues/>.
 
 SEE ALSO
 --------
 
 :manpage:`llvm-nm(1)`, :manpage:`llvm-objdump(1)`

llvm/docs/CommandGuide/llvm-size.rst

 -----------
 
 :program:`llvm-size` exits with a non-zero exit code if there is an error.
 Otherwise, it exits with code 0.
 
 BUGS
 ----
 
-To report bugs, please visit <https://bugs.llvm.org/>.
+To report bugs, please visit <https://github.com/llvm/llvm-project/issues/>.

llvm/docs/CommandGuide/llvm-strings.rst

 -----------
 
 :program:`llvm-strings` exits with a non-zero exit code if there is an error.
 Otherwise, it exits with code 0.
 
 BUGS
 ----
 
-To report bugs, please visit <https://bugs.llvm.org/>.
+To report bugs, please visit <https://github.com/llvm/llvm-project/issues/>.

llvm/docs/CommandGuide/llvm-strip.rst

 -----------
 
 :program:`llvm-strip` exits with a non-zero exit code if there is an error.
 Otherwise, it exits with code 0.
 
 BUGS
 ----
 
-To report bugs, please visit <https://bugs.llvm.org/>.
+To report bugs, please visit <https://github.com/llvm/llvm-project/issues/>.
 
 SEE ALSO
 --------
 
 :manpage:`llvm-objcopy(1)`

llvm/docs/DeveloperPolicy.rst

 such as `llvm-commits
 <http://lists.llvm.org/mailman/listinfo/llvm-commits>`_, `cfe-commits
 <http://lists.llvm.org/mailman/listinfo/cfe-commits>`_, or `lldb-commits
 <http://lists.llvm.org/mailman/listinfo/lldb-commits>`_.  Reading the
 "commits" list and paying attention to changes being made by others is a good
 way to see what other people are interested in and watching the flow of the
 project as a whole.
 
+.. FIXME: Edit for LLVM Issues in Github.
+
 We recommend that active developers register an email account with `LLVM
 Bugzilla <https://bugs.llvm.org/>`_ and preferably subscribe to the `llvm-bugs
 <http://lists.llvm.org/mailman/listinfo/llvm-bugs>`_ email list to keep track
 of bugs and enhancements occurring in LLVM.  We really appreciate people who are
 proactive at catching incoming bugs in their components and dealing with them
 promptly.
 
 Please be aware that all public LLVM mailing lists are public and archived, and

llvm/docs/HowToReleaseLLVM.rst

#. Manually file a bug_ with the subject: "Merge r12345 into the X.Y branch",
    enter the commit(s) that you want merged in the "Fixed by Commit(s)" and mark
    it as a blocker of the current release bug.  Release bugs are given aliases
    in the form of release-x.y.z, so to mark a bug as a blocker for the 5.0.1
    release, just enter release-5.0.1 in the "Blocks" field.
 
 #. Reply to the commit email on llvm-commits for the revision to merge and cc
    the release manager.
 
+.. FIXME: Edit for LLVM Issues in Github.
 .. _bug: https://bugs.llvm.org/
 
 Release Patch Rules
 -------------------
 
 Below are the rules regarding patching the release branch:
 
 #. Patches applied to the release branch may only be applied by the release

llvm/docs/HowToSubmitABug.rst

 
 Basically you have to do two things at a minimum. First, decide whether the
 bug `crashes the compiler`_ or if the compiler is `miscompiling`_ the program
 (i.e., the compiler successfully produces an executable, but it doesn't run
 right). Based on what type of bug it is, follow the instructions in the
 linked section to narrow down the bug so that the person who fixes it will be
 able to find the problem more easily.
 
+.. FIXME: Edit for LLVM Issues in Github.
+
 Once you have a reduced test-case, go to `the LLVM Bug Tracking System
 <https://bugs.llvm.org/enter_bug.cgi>`_ and fill out the form with the
 necessary details (note that you don't need to pick a category, just use
 the "new-bugs" category if you're not sure).  The bug description should
 contain the following information:
 
 * All information necessary to reproduce the problem.
 * The reduced test-case that triggers the bug.

llvm/utils/gn/secondary/clang/include/clang/Config/BUILD.gn

 import("//clang/lib/ARCMigrate/enable.gni")
 import("//clang/lib/StaticAnalyzer/Frontend/enable.gni")
 import("//llvm/utils/gn/build/libs/xml/enable.gni")
 import("//llvm/utils/gn/build/write_cmake_config.gni")
 import("//llvm/version.gni")
 
 write_cmake_config("Config") {
   input = "config.h.cmake"
   output = "$target_gen_dir/config.h"
   values = [
-    "BUG_REPORT_URL=https://bugs.llvm.org/",
+    "BUG_REPORT_URL=https://github.com/llvm/llvm-project/issues/",
     "CLANG_DEFAULT_PIE_ON_LINUX=",
     "CLANG_DEFAULT_LINKER=",
     "CLANG_DEFAULT_STD_C=",
     "CLANG_DEFAULT_STD_CXX=",
     "CLANG_DEFAULT_CXX_STDLIB=",
     "CLANG_DEFAULT_RTLIB=",
     "CLANG_DEFAULT_OBJCOPY=objcopy",
     "CLANG_DEFAULT_OPENMP_RUNTIME=libomp",

llvm/utils/gn/secondary/llvm/include/llvm/Config/BUILD.gn

 }
 
 write_cmake_config("config") {
   public_deps = [ ":llvm-config" ]
 
   input = "config.h.cmake"
   output = "$target_gen_dir/config.h"
   values = [
-    "BUG_REPORT_URL=https://bugs.llvm.org/",
+    "BUG_REPORT_URL=https://github.com/llvm/llvm-project/issues/",
     "ENABLE_BACKTRACES=1",
     "ENABLE_CRASH_OVERRIDES=1",
     "BACKTRACE_HEADER=execinfo.h",
     "HAVE_CRASHREPORTERCLIENT_H=",
     "HAVE_DECL_FE_ALL_EXCEPT=1",
     "HAVE_DECL_FE_INEXACT=1",
     "LLVM_ENABLE_CRASH_DUMPS=",
     "HAVE_ERRNO_H=1",
values = [
     "HAVE____CHKSTK=",
     "HAVE____CHKSTK_MS=",
     "HOST_LINK_VERSION=",
     "LIBPFM_HAS_FIELD_CYCLES=",
     "LLVM_TARGET_TRIPLE_ENV=",
     "LLVM_VERSION_INFO=",
     "LLVM_VERSION_PRINTER_SHOW_HOST_TARGET_INFO=1",
     "LLVM_WINDOWS_PREFER_FORWARD_SLASH=",
-    "PACKAGE_BUGREPORT=https://bugs.llvm.org/",
+    "PACKAGE_BUGREPORT=https://github.com/llvm/llvm-project/issues/",
     "PACKAGE_NAME=LLVM",
     "PACKAGE_STRING=LLVM ${llvm_version}git",
     "PACKAGE_VERSION=${llvm_version}git",
     "PACKAGE_VENDOR=",
     "RETSIGTYPE=void",
     "LLVM_GISEL_COV_ENABLED=",
     "LLVM_GISEL_COV_PREFIX=",
 

utils/bazel/llvm-project-overlay/clang/include/clang/Config/config.h

/* This is a manual port of config.h.cmake for the symbols that do not change
    that looks wrong, it probably is. */
 
 #ifdef CLANG_CONFIG_H
 #error config.h can only be included once
 #else
 #define CLANG_CONFIG_H
 
 /* Bug report URL. */
-#define BUG_REPORT_URL "https://bugs.llvm.org/"
+#define BUG_REPORT_URL "https://github.com/llvm/llvm-project/issues/"
 
 /* Default to -fPIE and -pie on Linux. */
 #define CLANG_DEFAULT_PIE_ON_LINUX 0
 
 /* Default linker to use. */
 #define CLANG_DEFAULT_LINKER ""
 
 /* Default C/ObjC standard to use. */

utils/bazel/llvm-project-overlay/llvm/include/llvm/Config/config.h

 
 // Include this header only under the llvm source tree.
 // This is a private header.
 
 /* Exported configuration */
 #include "llvm/Config/llvm-config.h"
 
 /* Bug report URL. */
-#define BUG_REPORT_URL "https://bugs.llvm.org/"
+#define BUG_REPORT_URL "https://github.com/llvm/llvm-project/issues/"
 
 /* Define to 1 to enable backtraces, and to 0 otherwise. */
 #define ENABLE_BACKTRACES 1
 
 /* Define to 1 to enable crash overrides, and to 0 otherwise. */
 #define ENABLE_CRASH_OVERRIDES 1
 
 /* Define to 1 to enable crash memory dumps, and to 0 otherwise. */

 
 /* Define if libxml2 is supported on this platform. */
 /* #undef LLVM_ENABLE_LIBXML2 */
 
 /* Define to the extension used for shared libraries, say, ".so". */
 /* LTDL_SHLIB_EXT defined in Bazel */
 
 /* Define to the address where bug reports for this package should be sent. */
-#define PACKAGE_BUGREPORT "https://bugs.llvm.org/"
+#define PACKAGE_BUGREPORT "https://github.com/llvm/llvm-project/issues/"
 
 /* Define to the full name of this package. */
 #define PACKAGE_NAME "LLVM"
 
 /* Define to the full name and version of this package. */
 #define PACKAGE_STRING PACKAGE_NAME " " LLVM_VERSION_STRING
 
 /* Define to the version of this package. */