Merge pull request open-telemetry#31 from signalfx/flands-patch-1

Create lychee.yml

.github/workflows/lychee-push.yml

@@ -0,0 +1,13 @@
+on: push
+jobs:
+  linkChecker:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: lychee Link Checker
+        id: lychee
+        uses: lycheeverse/[email protected]
+        with:
+          args: -v -n "*.md" "**/*.md"
+      - name: Fail if there were link errors
+        run: exit ${{ steps.lychee.outputs.exit_code }}

.github/workflows/lychee-weekly.yml

@@ -0,0 +1,18 @@
+on:
+  schedule:
+    - cron: "0 0 * * 1"
+jobs:
+  linkChecker:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: Link Checker
+        uses: lycheeverse/[email protected]
+        with:
+          args: -v -n "*.md" "**/*.md"
+      - name: Create Issue From File
+        uses: peter-evans/create-issue-from-file@v2
+        with:
+          title: Link Checker Report
+          content-filepath: ./lychee/out.md
+          labels: report, automated issue

CODE_OF_CONDUCT.md

@@ -73,4 +73,4 @@ members of the project's leadership.
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
-available at https://www.contributor-covenant.org/version/2/0/code-of-conduct.html
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct/

README.md

@@ -41,13 +41,12 @@ in [BCP 14](https://tools.ietf.org/html/bcp14)
 [[RFC8174](https://tools.ietf.org/html/rfc8174)] when, and only when, they
 appear in all capitals, as shown here.
 
-An implementation of the [specification](./docs/overview.md) is not
-compliant if it fails to satisfy one or more of the "MUST", "MUST NOT",
-"REQUIRED", "SHALL", or "SHALL NOT" requirements defined in the
-[specification](./docs/overview.md). Conversely, an implementation of
-the [specification](./docs/overview.md) is compliant if it satisfies
-all the "MUST", "MUST NOT", "REQUIRED", "SHALL", and "SHALL NOT" requirements
-defined in the [specification](./docs/overview.md).
+An implementation of the GDI specification is not compliant if it fails to
+satisfy one or more of the "MUST", "MUST NOT", "REQUIRED", "SHALL", or "SHALL
+NOT" requirements defined in the GDI specification. Conversely, an
+implementation of the GDI specification is compliant if it satisfies all the
+"MUST", "MUST NOT", "REQUIRED", "SHALL", and "SHALL NOT" requirements defined
+in the GDI specification.
 
 ## Versioning the Specification
 
@@ -65,5 +64,4 @@ See [CONTRIBUTING.md](CONTRIBUTING.md) for details on contribution process.
 
 ## License
 
-By contributing, you agree that your contributions will be licensed under its
-[Apache 2.0 License](LICENSE).
+[Apache Software License version 2.0](./LICENSE).

docs/templates/CODE_OF_CONDUCT.md

@@ -73,4 +73,4 @@ members of the project's leadership.
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
-available at https://www.contributor-covenant.org/version/2/0/code-of-conduct.html
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct/