fix(docs): contributions contents (#2912)

* docs: contributions

Some URLs we're pointing to another repository

* Create conventions.md

* Update CONTRIBUTING.md

* Create .gitattributes

* Update conventions.md

* Update CONTRIBUTING.md

* Update conventions.md

* Update conventions.md

* Update docs/conventions.md

Co-authored-by: Copilot <[email protected]>

* Update conventions.md

* Update .gitattributes

* Update conventions.md

---------

Co-authored-by: Copilot <[email protected]>

Author: mfranzke

.gitattributes

@@ -0,0 +1,29 @@
+# adapted out of https://github.com/h5bp/html5-boilerplate/blob/main/.gitattributes and https://rehansaeed.com/gitattributes-best-practices/
+# Automatically normalize line endings for all text-based files
+# https://git-scm.com/docs/gitattributes#_end_of_line_conversion
+
+###############################
+# Git Line Endings            #
+###############################
+
+# Set default behaviour to automatically normalize line endings.
+* text=auto
+
+# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+
+# For the following file types, normalize line endings to LF on
+# checkin and prevent conversion to CRLF when they are checked out
+# (this is required in order to prevent newline related issues like,
+# for example, after the build script is run)
+
+.*      text eol=lf
+*.css   text eol=lf
+*.html  text eol=lf
+*.js    text eol=lf
+*.json  text eol=lf
+*.md    text eol=lf
+*.mjs   text eol=lf
+*.sh    text eol=lf
+*.txt   text eol=lf
+*.xml   text eol=lf
+*.yml   text eol=lf

docs/conventions.md

@@ -1,20 +1,30 @@
 ## Git commits conventions
 
-We're using [husky git hooks](https://www.npmjs.com/husky) in combination with [commitlint](https://www.npmjs.com/package/@commitlint/cli) according to <https://commitlint.js.org/#/concepts-commit-conventions>:
+We're using [husky git hooks](https://www.npmjs.com/husky) in combination with [commitlint](https://www.npmjs.com/package/@commitlint/cli) according to <https://commitlint.js.org/concepts/commit-conventions.html#concept-commit-conventions>:
 
 ```text
 type(scope?): subject
 body?
 footer?
 ```
 
-> Type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum]
+[Type must be one of the following](https://commitlint.js.org/reference/rules.html#type-enum):
 
-source: [commitlint documentation](https://commitlint.js.org/#/?id=test)
+- build
+- chore
+- ci
+- docs
+- feat
+- fix
+- perf
+- refactor
+- revert
+- style
+- test
 
 If you'd like to test your commit message previous to using it, you could test it on the command line:
 
-```terminal
+```shell
 echo 'foo: bar' | commitlint
 ```
 
@@ -26,10 +36,20 @@ The general code conventions are guaranteed by the following tools.
 
 Both the [`.editorconfig`](https://editorconfig.org/) and [`.gitattributes`](https://dev.to/deadlybyte/please-add-gitattributes-to-your-git-repository-1jld) ensure a consistent code structure and conventions through their configurations.
 
+### prettier
+
+The [prettier](https://github.com/db-ui/core/blob/main/docs/adr/code_style_formatter-prettier.adoc) tool provides a general code prettifying.
+
+## Linting
+
 ### xo
 
 The [xo](https://github.com/db-ui/core/blob/main/docs/adr/linting-xo.adoc) tool provides a general code linting mechanism.
 
-### prettier
+### yaml files via yamllint
+
+- [yamllint.readthedocs.io](https://yamllint.readthedocs.io/)
+
+### markdown files via markdownlint
 
-The [prettier](https://github.com/db-ui/core/blob/main/docs/adr/code_style_formatter-prettier.adoc) tool provides a general code prettfying.
+- [github.com/markdownlint/markdownlint](https://github.com/markdownlint/markdownlint/)