[llvm] b3cfcf9 - Fix the LLVM Sphinx bot

[Aaron Ballman via llvm-commits]

Author: Aaron Ballman
Date: 2023-08-15T11:18:49-04:00
New Revision: b3cfcf9443873bd7ea3270f943cb4a946b269f33

URL: https://github.com/llvm/llvm-project/commit/b3cfcf9443873bd7ea3270f943cb4a946b269f33
DIFF: https://github.com/llvm/llvm-project/commit/b3cfcf9443873bd7ea3270f943cb4a946b269f33.diff

LOG: Fix the LLVM Sphinx bot

Switch to using anonymous links to avoid the duplicate explicit target
errors found by:

https://lab.llvm.org/buildbot/#/builders/30/builds/38838

Added: 
    

Modified: 
    llvm/docs/DeveloperPolicy.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/DeveloperPolicy.rst b/llvm/docs/DeveloperPolicy.rst
index 33b9f397f83d15..bc307f6b675b02 100644
--- a/llvm/docs/DeveloperPolicy.rst
+++ b/llvm/docs/DeveloperPolicy.rst
@@ -357,10 +357,10 @@ Below are some guidelines about the format of the message itself:
 * It is acceptable to add metadata to the commit message to automate processes,
   including for downstream consumers. If the patch has been reviewed, add a
   link to its review page, as shown
-  `here <https://www.llvm.org/docs/Phabricator.html#committing-a-change>`_. If
+  `here <https://www.llvm.org/docs/Phabricator.html#committing-a-change>`__. If
   the patch fixes a bug in GitHub Issues, we encourage adding a reference to
   the issue being closed, as described
-  `here <https://llvm.org/docs/BugLifeCycle.html#resolving-closing-bugs>`_.
+  `here <https://llvm.org/docs/BugLifeCycle.html#resolving-closing-bugs>`__.
   Other kinds of metadata are also acceptable, including links to resources
   that are not available to the entire community. However, such links should
   not be used in place of making the commit message self-explanatory.