Merge branch 'main' into mx-psi/preserve-internal-repr

.github/workflows/changelog.yml

@@ -77,10 +77,10 @@ jobs:
       - name: Render .chloggen changelog entries
         run: make chlog-preview > changelog_preview.md
       - name: Install markdown-link-check
-        run: npm install -g markdown-link-check
+        run: npm install
       - name: Run markdown-link-check
         run: |
-          markdown-link-check \
+          npx --no -- markdown-link-check \
             --verbose \
             --config .github/workflows/check_links_config.json \
             changelog_preview.md \

.github/workflows/check-links.yaml

@@ -1,7 +1,7 @@
 name: check-links
 on:
   push:
-    branches: [ main ]
+    branches: [main]
   pull_request:
 
 concurrency:
@@ -39,11 +39,11 @@ jobs:
           fetch-depth: 0
 
       - name: Install markdown-link-check
-        run: npm install -g [email protected]
+        run: npm install
 
       - name: Run markdown-link-check
         run: |
-          markdown-link-check \
+          npx --no -- markdown-link-check \
             --verbose \
             --config .github/workflows/check_links_config.json \
             ${{needs.changedfiles.outputs.md}} \

.gitignore

@@ -31,3 +31,8 @@ benchmarks.txt
 
 # golang
 go.work*
+
+# npm (used for markdown-link-check)
+node_modules/*
+package-lock.json
+

cmd/mdatagen/README.md

@@ -1,5 +1,15 @@
 # Metadata Generator
 
+<!-- status autogenerated section -->
+| Status        |           |
+| ------------- |-----------|
+| Stability     | [alpha]: metrics   |
+| Issues        | [![Open issues](https://img.shields.io/github/issues-search/open-telemetry/opentelemetry-collector-contrib?query=is%3Aissue%20is%3Aopen%20label%3Acmd%2Fmdatagen%20&label=open&color=orange&logo=opentelemetry)](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues?q=is%3Aopen+is%3Aissue+label%3Acmd%2Fmdatagen) [![Closed issues](https://img.shields.io/github/issues-search/open-telemetry/opentelemetry-collector-contrib?query=is%3Aissue%20is%3Aclosed%20label%3Acmd%2Fmdatagen%20&label=closed&color=blue&logo=opentelemetry)](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues?q=is%3Aclosed+is%3Aissue+label%3Acmd%2Fmdatagen) |
+| [Code Owners](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#becoming-a-code-owner)    | [@dmitryax](https://www.github.com/dmitryax) |
+
+[alpha]: https://github.com/open-telemetry/opentelemetry-collector#alpha
+<!-- end autogenerated section -->
+
 Every component's documentation should include a brief description of the component and guidance on how to use it.
 There is also some information about the component (or metadata) that should be included to help end-users understand the current state of the component and whether it is right for their use case.
 Examples of this metadata about a component are:

connector/README.md

@@ -1,7 +1,7 @@
 # Connectors
 
 A connector is both an exporter and receiver. As the name suggests a Connector connects
-two pipelines: it consumes data as an exporter at the end of one pipeline and emits data
+two pipelines: it emits data as an exporter at the end of one pipeline and consumes data
 as a receiver at the start of another pipeline. It may consume and emit data of the same data
 type, or of different data types. A connector may generate and emit data to summarize the
 consumed data, or it may simply replicate or route data.

package.json

@@ -0,0 +1,5 @@
+{
+  "devDependencies": {
+    "markdown-link-check": "^3.11.2"
+  }
+}