Use link check from the CLI instead of an action

.github/workflows/link-check-deploy.yml

@@ -2,47 +2,20 @@ name: Check new links against deployment
 # This workflow "triggers" and skips on deployment because GitHub Actions /
 # Checks refuses to show the check on deployment_status
 on:
-  - deployment
   - deployment_status
 jobs:
   run:
-    name: Initialize
+    name: Link Check
     runs-on: ubuntu-latest
     if:
-      github.event.deployment.ref != 'master' &&
       github.event.deployment_status.state == 'success'
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v3
         with:
           fetch-depth: 0
-      - id: build_check
-        uses: LouisBrunner/[email protected]
+      - uses: actions/setup-node@v3
         with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          name: Report
-          status: queued
-      - name: Run Link Check
+          node-version: 16
+      - name: Check Links
         id: check
-        uses: iterative/[email protected]
-        with:
-          diff: master
-          configFile: config/link-check/config.yml
-          rootURL: '${{ github.event.deployment.payload.web_url }}'
-          output: checksAction
-      - uses: LouisBrunner/[email protected]
-        if: ${{ success() }}
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          check_id: ${{ steps.build_check.outputs.check_id }}
-          status: completed
-          conclusion: ${{ steps.check.outputs.conclusion }}
-          output: ${{ steps.check.outputs.output }}
-      - uses: LouisBrunner/[email protected]
-        if: ${{ failure() }}
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          check_id: ${{ steps.build_check.outputs.check_id }}
-          status: completed
-          conclusion: failure
-          output: >-
-            {"summary": "The Link Check script had an error!"}
+        run: 'npx repo-link-check -c config/link-check/config.yml -d master -f -r "${{ github.event.deployment.payload.web_url }}"'

content/blog/2022-05-24-MLEM-release.md

@@ -26,6 +26,16 @@ tags:
 With MLEM ML teams get a single tool to **run your models anywhere** that
 strikes to cover all model productionization scenarios you have.
 
+[full good link](https://www.google.com) [short good link](www.google.com)
+[shorter good link](google.com)
+[full bad link](https://www.google.com/adddddbnbe)
+[short bad link](www.google.com/adddddbnbe)
+[shorter bad link](google.com/adddddbnbe)
+
+https://www.google.com
+
+https://www.google.com/adbbne
+
 MLEM enables this via **model metadata codification**: saving all information
 that is required to use a model later. Besides packaging a model for deployment
 it can be used for many things, including search and documentation. To make it