Bump yamllint version

Author: thomasleplus

.github/pull_request_template.md

@@ -0,0 +1,12 @@
+<!-- prettier-ignore-start -->
+<!-- markdownlint-disable-next-line MD041 -->
+## Readiness checklist
+<!-- prettier-ignore-end -->
+
+Please check the boxes below to confirm that you have followed the
+required guidelines for contributions:
+
+- [ ] If this pull request includes code changes, they were all properly tested. Automated tests where also included where possible.
+- [ ] This pull request includes the relevant documentation for this change (if applicable).
+- [ ] All the commits in this pull request where squashed into a single commit. That commit is [signed](https://docs.github.com/en/authentication/managing-commit-signature-verification).
+- [ ] If this pull request is about and existing issue, I added the `Fix #ISSUE_NUMBER` or `Close #ISSUE_NUMBER` text to the description of the pull request.

.github/workflows/yamllint.yml

@@ -20,7 +20,7 @@ jobs:
       - name: Install YAMLLint
         shell: bash
         run: |
-          pip install yamllint==1.36.0
+          pip install yamllint==1.36.1
           msg="$(pip list --outdated | grep -e yamllint || true)"
           if [ -n "${msg}" ]; then
             >&2 echo "ERROR: outdated: ${msg}"

CONTRIBUTING.md

@@ -0,0 +1,30 @@
+# Contributing
+
+## Creating an issue
+
+If you have found a bug, want to request an enhancement or simply ask
+a question, feel free to open an
+[issue](https://github.com/thomasleplus/java-sql-inspector/issues/new/choose).
+
+For security-related issues, please see our [security policy](/SECURITY.md).
+
+## Submitting a pull request
+
+If you want to contribute code, documentation etc. you can open a pull
+request. We then kindly ask that:
+
+- before working or submitting a large pull request, please open an
+  issue to discuss what you have in mind and check that there is not
+  an existing solution or a different approach.
+- all code changes must be tested manually and automated tests should
+  be included when possible.
+- all necessary documentation should be included as well.
+- commits on a single pull request must be squashed together to keep
+  make reviews easier.
+- commits must be signed (this is supported by most Git clients as
+  well as the GitHub web UI, see link below).
+
+## Resources
+
+- [Managing commit signature verification](https://docs.github.com/en/authentication/managing-commit-signature-verification)
+- [Using Pull Requests](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)

pom.xml

@@ -77,7 +77,7 @@
     <dependency>
       <groupId>org.junit.jupiter</groupId>
       <artifactId>junit-jupiter</artifactId>
-      <version>5.12.0</version>
+      <version>5.12.1</version>
       <scope>test</scope>
     </dependency>
     <dependency>