ci(automation): add link checking

.github/workflows/link-checker.yml

@@ -0,0 +1,19 @@
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    types: [opened, synchronize, reopened]
+  workflow_dispatch:
+name: Link Checker
+jobs:
+  linkinator:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: JustinBeckwith/linkinator-action@v1
+        with:
+          paths: "**/*.md"
+          markdown: true
+          retry: true
+          linksToSkip: "https://github.com/openjs-foundation/directory-private"

CODE_OF_CONDUCT.md

@@ -22,7 +22,7 @@ For reporting issues in spaces related to a member project, please use the email
 * AMP Project - `code-of-conduct@amp.dev`
 * Appium - [email maintainers]
 * Architect - 
-* Dojo - [reporting form](https://docs.google.com/forms/d/1ZiCUv3FsarWetoQ8J5QnCdIrHLj0xMmwNSLCyBkio7c/viewform?edit_requested=true)
+* Dojo - `report@lists.openjsf.org`
 * Electron - `coc@electronjs.org`
 * ESLint - `report@lists.openjsf.org`
 * Esprima - 

FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md

@@ -11,7 +11,7 @@ of the foundation.
 ## Code of Conduct
 
 The Foundation has adopted the
-[Contributor Covenant v2.0](https://www.contributor-covenant.org/version/2/0/code-of-conduct.md)
+[Contributor Covenant v2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/)
 as its code of conduct and it applies to all foundation activities and spaces. In
 addition, projects joining the foundation are required to adopt this code of conduct
 within 3 months of joining the foundation.

PROJECT_CHARTER_TEMPLATE.md

@@ -21,7 +21,7 @@ _to a colleague who is familiar with related technical concepts but unfamiliar_
 _with the project. You may also want to describe the project's value to community_
 _and/or business stakeholders._
 
-ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob//blob/HEAD/sig-architecture/charter.md#scope)
+ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob/HEAD/sig-architecture/charter.md#scope)
 
 ### 1.1: In-scope (optional)
 
@@ -31,7 +31,7 @@ _apparent. This may help differentiate the project from other solutions in the_
 _space. If you are not using this section, please indicate your intent with the_
 _phrase, 'Section Intentionally Left Blank'._
 
-ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob//blob/HEAD/sig-architecture/charter.md#in-scope)
+ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob/HEAD/sig-architecture/charter.md#in-scope)
 
 ### 1.2: Out-of-Scope (optional)
 
@@ -41,7 +41,7 @@ _features, contributions, issues or problems the project is looking for._
 _If you are not using this section, please indicate your intent with the_
 _phrase, 'Section Intentionally Left Blank'._
 
-ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob//blob/HEAD/sig-architecture/charter.md#out-of-scope)
+ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob/HEAD/sig-architecture/charter.md#out-of-scope)
 
 ## Section 2: Relationship with OpenJS Foundation CPC.
 
@@ -70,7 +70,7 @@ ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md
 
 _directions: describe the roles and responsibilities of the ${PROJECT} Governing Body._
 
-ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob//blob/HEAD/sig-architecture/charter.md#roles-and-organization-management)
+ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob/HEAD/sig-architecture/charter.md#roles-and-organization-management)
 ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md#section-4-responsibilities-of-the-tsc)
 
 ### Section 4.1 Project Operations & Management (optional)
@@ -80,7 +80,7 @@ _${PROJECT} Governing Body may be responsible for regarding process or project_
 _operations and management. If you are not using this section, please indicate_
 _your intent with the phrase, 'Section Intentionally Left Blank'._
 
-ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob//blob/HEAD/sig-architecture/charter.md#roles-and-organization-management)
+ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob/HEAD/sig-architecture/charter.md#roles-and-organization-management)
 ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md#section-5-nodejs-project-operations)
 
 ### Section 4.2: Decision-making, Voting, and/or Elections (optional)

PROJECT_PROGRESSION.md

@@ -259,8 +259,8 @@ This is an informational checklist to help projects move to Emeritus Stage. Task
 - [ ] Archive the project
 - [ ] Move [project logo](https://github.com/openjs-foundation/artwork) to Emeritus Stage section
 - [ ] Move project logo on OpenJS Foundation website to Emeritus Stage section
-- [ ] Mark project in the [CPC repo's README.md](https://github.com/openjs-foundation/cross-project-council/blob/master/README.md#incubating-projects) as Emeritus
-- [ ] Update security policy (see [PROJECT_SECURITY_REPORTING](https://github.com/openjs-foundation/cross-project-council/blob/master/PROJECT_SECURITY_REPORTING.md))
+- [ ] Mark project in the [CPC repo's README.md](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/README.md#incubating-projects) as Emeritus
+- [ ] Update security policy (see [PROJECT_SECURITY_REPORTING](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/PROJECT_SECURITY_REPORTING.md))
 
 
 ## VI. Annual Review Process