doc: add ADOPTERS.md to the project (dyrector-io#835)

.github/config/title_label_config.yml

@@ -1,4 +1,5 @@
-pr:cicd: [^cicd]
+pr:build: [^build]
+pr:ci: [^ci]
 pr:chore: [^chore]
 pr:doc: [^doc]
 pr:feat: [^feat]

ADOPTERS.md

@@ -0,0 +1,25 @@
+# Adopters
+
+This list captures the set of organizations that are using dyrector.io platform within their environments. If
+you are an adopter of dyrector.io platform and not yet on this list, we encourage you to add your organization
+here as well!
+
+The goal for this list is to be the complete and authoritative source for the entire community of
+dyrector.io platform adopters, and give inspiration to others that are earlier in their dyrector.io journey.
+
+Contributing to this list is a small effort that has a **big impact** to the project's growth,
+maturity, and momentum. Thank you to all adopters and contributors of the project!
+
+## Updating this list
+
+To add your organization to this list, you can [Open a PR](https://github.com/dyrector-io/dyrectorio/pulls) to update this list directly after reading the [contributing documentation](./CONTRIBUTING.md).
+
+Feel free to reach out to <[email protected]> with any questions and/or assistance with updating this list.
+
+## Adopters
+
+This list is sorted in the order that organizations were added to it.
+
+| Organization | Contact                        | Description of Use |
+| ------------ | ------------------------------ | ------------------ |
+| Example      | @example / or [email protected] | Lore ipsum         |

CONTRIBUTING.md

@@ -146,7 +146,7 @@ The commit contains the following structural elements, to communicate intent to
 1. **BREAKING CHANGE:** a commit that has a footer `BREAKING CHANGE:`, or appends a `!` after the type/scope, introduces a breaking API change (correlating with [`MAJOR`](http://semver.org/#summary) in Semantic Versioning).
    A BREAKING CHANGE can be part of commits of any _type_.
 1. _types_ other than `fix:` and `feat:` are allowed, for example [@commitlint/config-conventional](https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional) (based on the [the Angular convention](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines)) recommends `build:`, `chore:`,
-   `ci:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`, and others.
+   `ci:`, `doc:`, `style:`, `refactor:`, `test:`, and others.
 1. _footers_ other than `BREAKING CHANGE: <description>` may be provided and follow a convention similar to
    [git trailer format](https://git-scm.com/docs/git-interpret-trailers).