disabled failing linters and fixed markdown issues (prometheus-commun…

…ity#32) (prometheus-community#33)

Signed-off-by: Scott Rigby <scott@r6by.com>

.github/workflows/linter.yml

@@ -16,5 +16,10 @@ jobs:
         uses: github/super-linter@v3
         env:
           VALIDATE_ALL_CODEBASE: false
+          VALIDATE_BASH: false
+          VALIDATE_PYTHON: false
+          VALIDATE_PYTHON_FLAKE8: false
+          VALIDATE_PYTHON_BLACK: false
+          VALIDATE_YAML: false
           DEFAULT_BRANCH: main
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

CODE_OF_CONDUCT.md

@@ -1,3 +1,3 @@
-## Community Code of Conduct
+# Community Code of Conduct
 
 Prometheus follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).

CONTRIBUTING.md

@@ -6,15 +6,15 @@ Contributions are welcome via GitHub pull requests. This document outlines the p
 
 The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the [DCO](http://developercertificate.org/). Contributors must sign-off that they adhere to these requirements by adding a `Signed-off-by` line to commit messages.
 
-```
+```text
 This is my commit message
 
 Signed-off-by: Random J Developer <random@developer.example.org>
 ```
 
 See `git help commit`:
 
-```
+```text
 -s, --signoff
     Add Signed-off-by line by the committer at the end of the commit log
     message. The meaning of a signoff depends on the project, but it typically

README.md

@@ -12,7 +12,7 @@ Please refer to Helm's [documentation](https://helm.sh/docs/) to get started.
 Once Helm is set up properly, add the repo as follows:
 
 ```console
-$ helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
+helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
 ```
 
 You can then run `helm search repo prometheus-community` to see the charts.