Code of conduct + use existing dependencies label for dependabot (#136)

* break out code of conduct for visibility

* use existing dependencies label for dependabot

Author: AshleyDumaine

.github/dependabot.yml

@@ -9,7 +9,7 @@ updates:
     commit-message:
       prefix: ":seedling:"
     labels:
-      - "kind/cleanup"
+      - "dependencies"
 
 # Docker
   - package-ecosystem: "docker"
@@ -19,7 +19,7 @@ updates:
     commit-message:
       prefix: ":seedling:"
     labels:
-      - "kind/cleanup"
+      - "dependencies"
 
 # github-actions
   - package-ecosystem: "github-actions"
@@ -29,4 +29,4 @@ updates:
     commit-message:
       prefix: ":seedling:"
     labels:
-      - "kind/cleanup"
+      - "dependencies"

CONTRIBUTING.md

@@ -56,10 +56,6 @@ All changes must be code reviewed. Coding conventions and standards are explaine
 
 In case you want to run our E2E tests locally, please refer to the [E2E Testing](https://linode.github.io/cluster-api-provider-linode/developers/development.html#e2e-testing) guide.
 
-## Code of Conduct
-
-This project follows the [Linode Community Code of Conduct](https://www.linode.com/community/questions/conduct). 
-
 ## Vulnerability Reporting
 
 If you discover a potential security issue in this project we ask that you notify Linode Security via our [vulnerability reporting process](https://hackerone.com/linode). Please do **not** create a public github issue.

code-of-conduct.md

@@ -0,0 +1,4 @@
+## Linode Community Code of Conduct
+
+This project follows the [Linode Community Code of Conduct](https://www.linode.com/community/questions/conduct). 
+