Add VCS metrics from Github receiver

.chloggen/1372-vcs-metrics.yaml

@@ -0,0 +1,22 @@
+# Use this changelog template to create an entry for release notes.
+#
+# If your change doesn't affect end users you should instead start
+# your pull request title with [chore] or use the "Skip Changelog" label.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: enhancement
+
+# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
+component: vcs
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add the VCS metrics from the GitHub Receiver
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+# The values here must be integers.
+issues: [1372]
+
+# (Optional) One or more lines of additional information to render under the primary note.
+# These lines will be padded with 2 spaces and then inserted directly into the document.
+# Use pipe (|) for multiline entries.
+subtext:

docs/README.md

@@ -21,6 +21,7 @@ The benefit to using Semantic Conventions is in following a common naming scheme
 Semantic Conventions are defined for the following areas:
 
 * **[General](general/README.md): General Semantic Conventions**.
+* [CICD](cicd/cicd-metrics.md): Semantic Conventions for CICD systems.
 * [Cloud Providers](cloud-providers/README.md): Semantic Conventions for cloud providers libraries.
 * [CloudEvents](cloudevents/README.md): Semantic Conventions for the CloudEvents specification.
 * [Database](database/README.md): Semantic Conventions for database operations.

docs/attributes-registry/vcs.md

@@ -12,8 +12,10 @@ This group defines the attributes for [Version Control Systems (VCS)](https://en
 
 | Attribute                     | Type   | Description                                                                                                                                                                                | Examples                                                                                                                             | Stability                                                        |
 | ----------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------- |
+| `vcs.change.state`            | string | The state of the change (pull request/merge request).                                                                                                                                      | `open`; `closed`; `merged`                                                                                                           | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `vcs.repository.change.id`    | string | The ID of the change (pull request/merge request) if applicable. This is usually a unique (within repository) identifier generated by the VCS system.                                      | `123`                                                                                                                                | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `vcs.repository.change.title` | string | The human readable title of the change (pull request/merge request). This title is often a brief summary of the change and may get merged in to a ref as the commit summary.               | `Fixes broken thing`; `feat: add my new feature`; `[chore] update dependency`                                                        | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+| `vcs.repository.name`         | string | The name of the repository.                                                                                                                                                                | `open-telemetry-collector-contrib`; `opentelemetry/open-telemetry-collector-contrib`; `my-org/my-project/my-projects-project`        | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `vcs.repository.ref.name`     | string | The name of the [reference](https://git-scm.com/docs/gitglossary#def_ref) such as **branch** or **tag** in the repository.                                                                 | `my-feature-branch`; `tag-1-test`                                                                                                    | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `vcs.repository.ref.revision` | string | The revision, literally [revised version](https://www.merriam-webster.com/dictionary/revision), The revision most often refers to a commit object in Git, or a revision number in SVN. [1] | `9d59409acf479dfa0df1aa568182e43e43df8bbe28d60fcf2bc52e30068802cc`; `main`; `123`; `HEAD`                                            | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `vcs.repository.ref.type`     | string | The type of the [reference](https://git-scm.com/docs/gitglossary#def_ref) in the repository.                                                                                               | `branch`; `tag`                                                                                                                      | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
@@ -29,6 +31,14 @@ it is identical to the `ref.name`, it SHOULD still be included. It is
 up to the implementer to decide which value to set as the revision
 based on the VCS system and situational context.
 
+`vcs.change.state` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
+
+| Value    | Description                                                                                    | Stability                                                        |
+| -------- | ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
+| `closed` | closed                                                                                         | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+| `merged` | [merged](https://git-scm.com/docs/gitglossary#Documentation/gitglossary.txt-aiddeftagatag)     | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+| `open`   | [open](https://git-scm.com/docs/gitglossary#Documentation/gitglossary.txt-aiddefbranchabranch) | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+
 `vcs.repository.ref.type` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
 
 | Value    | Description                                                                                      | Stability                                                        |