docs(jobs): add code block patterns to link check config (#83)

.mlc_config.json

@@ -15,8 +15,20 @@
   {
     "pattern": "^https:\/\/api.github.com"
   },
+  {
+    "pattern": "((http([s]){0,1}:\/\/){0,1}(localhost|127.0.0.1){1}(([:]){0,1}[\0-9]{4}){0,1}\/{0,1}){1}"
+  },
   {
     "pattern": "^#[a-zA-Z0-9-]*"
+  },
+  {
+    "pattern": "(?s) *({{< highlight [^>]* ?>}}.*?{{< ?/ ?highlight >}})"
+  },
+  {
+    "pattern": "(?s) *(\x60\x60\x60.*?\x60\x60\x60)"
+  },
+  {
+    "pattern": "^https:\/\/twitter.com"
   }
 ],
   "aliveStatusCodes": [

content/en/deployment/kubernetes/argo-rollouts.md

@@ -110,7 +110,6 @@ See {{< linkWithTitle "reference/deployment/_index.md" >}} if you want to create
 
 You can use webhooks in `afterDeployment` constraints to add specific logic for Argo Rollouts to finish deploying before starting integration tests. For example:
 
-<!-- markdown-link-check-disable -->
 {{< highlight yaml "linenos=table,hl_lines=9-12 15-28" >}}
  # armoryDeployment.yaml
 version: v1
@@ -141,7 +140,6 @@ webhooks:
         "callbackURL": "{{armory.callbackUri}}/callback"
         }
 {{< /highlight >}}
-<!-- markdown-link-check-enable-->
 
 This example employs [cmd-hook](https://hub.docker.com/r/demoimages/cmd-hook), which is an open source service deployed in the cluster to execute `kubectl` commands. CD-as-a-Service employs RNA to execute `kubectl` commands for monitoring the state of rollout objects. You can view the source code for `cmd-hook` in the [public repository](https://github.com/stephenatwell/cmdHook).