summaryrefslogtreecommitdiffstats
path: root/clang-tools-extra/docs/clang-tidy/Contributing.rst
diff options
context:
space:
mode:
Diffstat (limited to 'clang-tools-extra/docs/clang-tidy/Contributing.rst')
-rw-r--r--clang-tools-extra/docs/clang-tidy/Contributing.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/clang-tools-extra/docs/clang-tidy/Contributing.rst b/clang-tools-extra/docs/clang-tidy/Contributing.rst
index 6d61809ecb3..719bed38f23 100644
--- a/clang-tools-extra/docs/clang-tidy/Contributing.rst
+++ b/clang-tools-extra/docs/clang-tidy/Contributing.rst
@@ -127,7 +127,7 @@ style used in the project. For code reviews we mostly use `LLVM Phabricator`_.
Next, you need to decide which module the check belongs to. Modules
are located in subdirectories of `clang-tidy/
-<https://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/>`_
+<https://github.com/llvm/llvm-project/tree/master/clang-tools-extra/clang-tidy/>`_
and contain checks targeting a certain aspect of code quality (performance,
readability, etc.), certain coding style or standard (Google, LLVM, CERT, etc.)
or a widely used API (e.g. MPI). Their names are same as user-facing check
@@ -210,7 +210,7 @@ can further inspect them and report diagnostics.
(If you want to see an example of a useful check, look at
`clang-tidy/google/ExplicitConstructorCheck.h
-<https://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/google/ExplicitConstructorCheck.h>`_
+<https://github.com/llvm/llvm-project/blob/master/clang-tools-extra/clang-tidy/google/ExplicitConstructorCheck.h>`_
and `clang-tidy/google/ExplicitConstructorCheck.cpp
<https://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/google/ExplicitConstructorCheck.cpp>`_).
OpenPOWER on IntegriCloud