chore: check links only in modified files (#394)

* chore: check links only in modified files Signed-off-by: Yue Yang <g1enyy0ung@gmail.com> * fix: links Signed-off-by: Yue Yang <g1enyy0ung@gmail.com> * fix: config Signed-off-by: Yue Yang <g1enyy0ung@gmail.com> * fix: mlc_config Signed-off-by: Yue Yang <g1enyy0ung@gmail.com> * fix: links and meituan logo Signed-off-by: Yue Yang <g1enyy0ung@gmail.com> * check-modified-files-only Signed-off-by: Yue Yang <g1enyy0ung@gmail.com> --------- Signed-off-by: Yue Yang <g1enyy0ung@gmail.com>
chaos-mesh · Aug 7, 2023 · 0692fd2 · 0692fd2
1 parent f9cb8b4
commit 0692fd2
Show file tree

Hide file tree

Showing 16 changed files with 36 additions and 50 deletions.
diff --git a/.github/workflows/markdown-link-check.json b/.github/workflows/markdown-link-check.json
diff --git a/.github/workflows/markdown-link-check.yaml b/.github/workflows/markdown-link-check.yaml
@@ -6,22 +6,22 @@ on:
       - master
     paths:
       - '**.md'
-      - '.github/workflows/markdown-link-check.json'
+      - 'mlc_config.json'
   pull_request:
     branches:
       - master
     paths:
       - '**.md'
-      - '.github/workflows/markdown-link-check.json'
+      - 'mlc_config.json'
 
 permissions: read-all
 
 jobs:
   markdown-link-check:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@master
+      - uses: actions/checkout@v3
       - uses: gaurav-nelson/github-action-markdown-link-check@v1
         with:
           use-quiet-mode: 'yes'
-          config-file: '.github/workflows/markdown-link-check.json'
+          check-modified-files-only: 'yes'
diff --git a/...4-20-simulating-clock-skew-in-k8s-without-affecting-other-containers-on-node.md b/...4-20-simulating-clock-skew-in-k8s-without-affecting-other-containers-on-node.md
@@ -98,7 +98,7 @@ The chart above is the process of **TimeChaos**, an implementation of clock skew
 4. Use ptrace to modify the `clock_gettime` function in vDSO and redirect to the `fake_clock_gettime` function.
 5. Use ptrace to detach the PID process.
 
-If you are interested in the details, see the [Chaos Mesh GitHub repository](https://github.com/chaos-mesh/chaos-mesh/blob/master/pkg/time/time_linux.go).
+If you are interested in the details, see the [Chaos Mesh GitHub repository](https://github.com/chaos-mesh/chaos-mesh/blob/release-1.0/pkg/time/time_linux.go).
 
 ## Simulating clock skew on a distributed SQL database
 

diff --git a/blog/2020-07-28-chaos-mesh-join-cncf-sandbox-project.md b/blog/2020-07-28-chaos-mesh-join-cncf-sandbox-project.md
@@ -24,7 +24,7 @@ Within only 7 months since it was open-sourced on December 31st, 2019, Chaos Mes
 - [NetEase Fuxi Lab](https://fuxi.163.com/fuxi-introduction)
 - [JuiceFS](http://juicefs.com/en)
 - [Dailymotion](https://www.dailymotion.com/)
-- [Meituan-Dianping](https://about.meituan.com/en)
+- [Meituan](https://www.meituan.com/en-US/about-us)
 - [Celo](https://celo.org/)
 
 Being a CNCF Sandbox project marks a major step forward for the project. It means that Chaos Mesh has become part of the great vendor-neutral cloud-native community. With the guidance and help from CNCF, Chaos Mesh will strive to develop a community with transparent, meritocracy-based governance for open communication and open collaboration, while driving the project forward, towards our ultimate goal of establishing the Chaos Engineering standards on Cloud. Currently, Chaos Mesh is in active development for 1.0 GA. Going forward, we will be focusing on the following aspects:

diff --git a/docs/extend-chaos-daemon-interface.md b/docs/extend-chaos-daemon-interface.md
@@ -246,6 +246,6 @@ Now you can verify the output of `HelloWorldChaos`:
 
 If you encounter any problems during the process, create an [issue](https://github.com/chaos-mesh/chaos-mesh/issues) in the Chaos Mesh repository.
 
-If you are curious about how all this works, you can read the [controllers/README.md](https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/README.md) and related files next.
+If you are curious about how all this works, you can read the [controllers/README.md](https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/README.md) and code for different controllers next.
 
 You are now ready to become a Chaos Mesh developer! Feel free to visit the [Chaos Mesh issues](https://github.com/chaos-mesh/chaos-mesh/issues) to find a [good first issue](https://github.com/chaos-mesh/chaos-mesh/labels/good%20first%20issue) and get started!
diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/extend-chaos-daemon-interface.md b/i18n/zh/docusaurus-plugin-content-docs/current/extend-chaos-daemon-interface.md
@@ -6,7 +6,7 @@ title: 拓展 Chaos Daemon 接口
 
 :::note 注意
 
-一些关于 Chaos Mesh 架构的知识对于帮助你理解这一文档非常有用，例如 [Chaos Mesh  架构](architecture.md)。
+一些关于 Chaos Mesh 架构的知识对于帮助你理解这一文档非常有用，例如 [Chaos Mesh 架构](./overview.md#架构概览)。
 
 :::
 
@@ -283,6 +283,6 @@ func (obj *HelloWorldChaos) GetSelectorSpecs() map[string]interface{} {
 
 在完成上述步骤后，HelloWorldChaos 已经成为一种有实际作用的混沌实验。如果你在这一过程中遇到了问题，请在 GitHub 创建一个 [issue](https://github.com/pingcap/chaos-mesh/issues) 向 Chaos Mesh 团队反馈。
 
-你可能很好奇这一切是如何生效的。可以试着看看 `controllers` 目录下的各类 `controller`，它们有自己的 README（如 [controllers/common/README.md](https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/common/README.md)）。你可以通过这些 README 了解每个 controller 的功能，也可以阅读 [Chaos Mesh  架构](architecture.md)了解 Chaos Mesh 背后的原理。
+如果您想知道所有这些是如何工作的，您可以稍后阅读 [controllers/README.md](https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/README.md) 和不同控制器的代码。
 
 你已经准备好成为一名真正的 Chaos Mesh 开发者了！到 [Chaos Mesh](https://github.com/chaos-mesh/chaos-mesh) 里找一找练手的任务吧！推荐你先从简单的入手，例如这些 [good first issues](https://github.com/chaos-mesh/chaos-mesh/labels/good%20first%20issue)。
diff --git a/...h/docusaurus-plugin-content-docs/version-2.4.3/extend-chaos-daemon-interface.md b/...h/docusaurus-plugin-content-docs/version-2.4.3/extend-chaos-daemon-interface.md
@@ -6,7 +6,7 @@ title: 拓展 Chaos Daemon 接口
 
 :::note 注意
 
-一些关于 Chaos Mesh 架构的知识对于帮助你理解这一文档非常有用，例如 [Chaos Mesh  架构](architecture.md)。
+一些关于 Chaos Mesh 架构的知识对于帮助你理解这一文档非常有用，例如 [Chaos Mesh 架构](./overview.md#架构概览)。
 
 :::
 
@@ -283,6 +283,6 @@ func (obj *HelloWorldChaos) GetSelectorSpecs() map[string]interface{} {
 
 在完成上述步骤后，HelloWorldChaos 已经成为一种有实际作用的混沌实验。如果你在这一过程中遇到了问题，请在 GitHub 创建一个 [issue](https://github.com/pingcap/chaos-mesh/issues) 向 Chaos Mesh 团队反馈。
 
-你可能很好奇这一切是如何生效的。可以试着看看 `controllers` 目录下的各类 `controller`，它们有自己的 README（如 [controllers/common/README.md](https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/common/README.md)）。你可以通过这些 README 了解每个 controller 的功能，也可以阅读 [Chaos Mesh  架构](architecture.md)了解 Chaos Mesh 背后的原理。
+如果您想知道所有这些是如何工作的，您可以稍后阅读 [controllers/README.md](https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/README.md) 和不同控制器的代码。
 
 你已经准备好成为一名真正的 Chaos Mesh 开发者了！到 [Chaos Mesh](https://github.com/chaos-mesh/chaos-mesh) 里找一找练手的任务吧！推荐你先从简单的入手，例如这些 [good first issues](https://github.com/chaos-mesh/chaos-mesh/labels/good%20first%20issue)。
diff --git a/...h/docusaurus-plugin-content-docs/version-2.5.2/extend-chaos-daemon-interface.md b/...h/docusaurus-plugin-content-docs/version-2.5.2/extend-chaos-daemon-interface.md
@@ -6,7 +6,7 @@ title: 拓展 Chaos Daemon 接口
 
 :::note 注意
 
-一些关于 Chaos Mesh 架构的知识对于帮助你理解这一文档非常有用，例如 [Chaos Mesh  架构](architecture.md)。
+一些关于 Chaos Mesh 架构的知识对于帮助你理解这一文档非常有用，例如 [Chaos Mesh 架构](./overview.md#架构概览)。
 
 :::
 
@@ -283,6 +283,6 @@ func (obj *HelloWorldChaos) GetSelectorSpecs() map[string]interface{} {
 
 在完成上述步骤后，HelloWorldChaos 已经成为一种有实际作用的混沌实验。如果你在这一过程中遇到了问题，请在 GitHub 创建一个 [issue](https://github.com/pingcap/chaos-mesh/issues) 向 Chaos Mesh 团队反馈。
 
-你可能很好奇这一切是如何生效的。可以试着看看 `controllers` 目录下的各类 `controller`，它们有自己的 README（如 [controllers/common/README.md](https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/common/README.md)）。你可以通过这些 README 了解每个 controller 的功能，也可以阅读 [Chaos Mesh  架构](architecture.md)了解 Chaos Mesh 背后的原理。
+如果您想知道所有这些是如何工作的，您可以稍后阅读 [controllers/README.md](https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/README.md) 和不同控制器的代码。
 
 你已经准备好成为一名真正的 Chaos Mesh 开发者了！到 [Chaos Mesh](https://github.com/chaos-mesh/chaos-mesh) 里找一找练手的任务吧！推荐你先从简单的入手，例如这些 [good first issues](https://github.com/chaos-mesh/chaos-mesh/labels/good%20first%20issue)。
diff --git a/...h/docusaurus-plugin-content-docs/version-2.6.1/extend-chaos-daemon-interface.md b/...h/docusaurus-plugin-content-docs/version-2.6.1/extend-chaos-daemon-interface.md
@@ -6,7 +6,7 @@ title: 拓展 Chaos Daemon 接口
 
 :::note 注意
 
-一些关于 Chaos Mesh 架构的知识对于帮助你理解这一文档非常有用，例如 [Chaos Mesh  架构](architecture.md)。
+一些关于 Chaos Mesh 架构的知识对于帮助你理解这一文档非常有用，例如 [Chaos Mesh 架构](./overview.md#架构概览)。
 
 :::
 
@@ -283,6 +283,6 @@ func (obj *HelloWorldChaos) GetSelectorSpecs() map[string]interface{} {
 
 在完成上述步骤后，HelloWorldChaos 已经成为一种有实际作用的混沌实验。如果你在这一过程中遇到了问题，请在 GitHub 创建一个 [issue](https://github.com/pingcap/chaos-mesh/issues) 向 Chaos Mesh 团队反馈。
 
-你可能很好奇这一切是如何生效的。可以试着看看 `controllers` 目录下的各类 `controller`，它们有自己的 README（如 [controllers/common/README.md](https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/common/README.md)）。你可以通过这些 README 了解每个 controller 的功能，也可以阅读 [Chaos Mesh  架构](architecture.md)了解 Chaos Mesh 背后的原理。
+如果您想知道所有这些是如何工作的，您可以稍后阅读 [controllers/README.md](https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/README.md) 和不同控制器的代码。
 
 你已经准备好成为一名真正的 Chaos Mesh 开发者了！到 [Chaos Mesh](https://github.com/chaos-mesh/chaos-mesh) 里找一找练手的任务吧！推荐你先从简单的入手，例如这些 [good first issues](https://github.com/chaos-mesh/chaos-mesh/labels/good%20first%20issue)。
diff --git a/mlc_config.json b/mlc_config.json
@@ -0,0 +1,14 @@
+{
+  "ignorePatterns": [
+    {
+      "pattern": "^/img/"
+    },
+    {
+      "pattern": "run-a-chaos-experiment.md"
+    },
+    {
+      "pattern": "^http://localhost"
+    }
+  ],
+  "aliveStatusCodes": [200, 403, 500, 502, 503]
+}
diff --git a/src/data/whoIsUsing.js b/src/data/whoIsUsing.js
@@ -69,9 +69,9 @@ const whoisUsing = [
     href: 'https://www.maycur.com/',
   },
   {
-    name: 'Meituan Dianping',
-    img: 'img/logos/meituandianping.png',
-    href: 'https://about.meituan.com/',
+    name: 'Meituan',
+    img: 'img/logos/meituan.svg',
+    href: 'https://www.meituan.com/en-US/about-us',
   },
   {
     name: 'NETSTARS',

diff --git a/static/img/logos/meituan.svg b/static/img/logos/meituan.svg
diff --git a/static/img/logos/meituandianping.png b/static/img/logos/meituandianping.png
diff --git a/versioned_docs/version-2.4.3/extend-chaos-daemon-interface.md b/versioned_docs/version-2.4.3/extend-chaos-daemon-interface.md
@@ -283,6 +283,6 @@ To verify the experiment, perform the following steps.
 
 If you encounter any problems in this process, create an [issue](https://github.com/pingcap/chaos-mesh/issues) in the Chaos Mesh repository.
 
-If you are curious about how all of these come into effect, you can read the README files of different `controllers` in the `controller` directory to learn their functionalities. For example, [controllers/common/README.md](https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/common/README.md).
+If you are curious about how all of these come into effect, you can read the README files of different `controllers` in the `controller` directory to learn their functionalities. For example, [controllers/README.md](https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/README.md).
 
 Now you are ready to become a Chaos Mesh developer! You are welcome to visit the [Chaos Mesh](https://github.com/chaos-mesh/chaos-mesh) repository to find a [good first issue](https://github.com/chaos-mesh/chaos-mesh/labels/good%20first%20issue) and get started!
diff --git a/versioned_docs/version-2.5.2/extend-chaos-daemon-interface.md b/versioned_docs/version-2.5.2/extend-chaos-daemon-interface.md
@@ -283,6 +283,6 @@ To verify the experiment, perform the following steps.
 
 If you encounter any problems in this process, create an [issue](https://github.com/pingcap/chaos-mesh/issues) in the Chaos Mesh repository.
 
-If you are curious about how all of these come into effect, you can read the README files of different `controllers` in the `controller` directory to learn their functionalities. For example, [controllers/common/README.md](https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/common/README.md).
+If you are curious about how all of these come into effect, you can read the README files of different `controllers` in the `controller` directory to learn their functionalities. For example, [controllers/README.md](https://github.com/chaos-mesh/chaos-mesh/blob/master/controllers/README.md).
 
 Now you are ready to become a Chaos Mesh developer! You are welcome to visit the [Chaos Mesh](https://github.com/chaos-mesh/chaos-mesh) repository to find a [good first issue](https://github.com/chaos-mesh/chaos-mesh/labels/good%20first%20issue) and get started!