Bump gitguardian/ggshield from 1.13.3 to 1.13.5 (#25)

<!--pre-commit.ci start-->
updates:
- [github.com/Yelp/detect-secrets: v1.3.0 →
v1.4.0](Yelp/detect-secrets@v1.3.0...v1.4.0)
- [github.com/zricethezav/gitleaks: v8.13.0 →
v8.15.0](gitleaks/gitleaks@v8.13.0...v8.15.0)
- [github.com/gitguardian/ggshield: v1.13.3 →
v1.13.5](GitGuardian/ggshield@v1.13.3...v1.13.5)
<!--pre-commit.ci end-->

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: fabasoad <[email protected]>

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @fabasoad

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: fabasoad
+
+---
+
+## Describe the bug
+
+A clear and concise description of what the bug is.
+
+## Steps to Reproduce
+
+1. Run '...'
+2. See error
+
+## Expected behavior
+
+A clear and concise description of what you expected to happen.
+
+## Actual behavior
+
+A clear and concise description of what is happening now.
+
+## Screenshots
+
+If applicable, add screenshots to help explain your problem.
+
+## Technical information (please complete the following information)
+
+- OS: [e.g. Windows 10 Enterprise v.1909 (OS Build 18363.720)]
+- `pre-commit-snyk` version [e.g. 0.1.0]
+
+## Additional context
+
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,26 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: fabasoad
+
+---
+
+## Is your feature request related to a problem? Please describe
+
+A clear and concise description of what the problem is. Ex. I'm always frustrated
+when [...]
+
+## Describe the solution you'd like
+
+A clear and concise description of what you want to happen.
+
+## Describe alternatives you've considered
+
+A clear and concise description of any alternative solutions or features you've
+considered.
+
+## Additional context
+
+Add any other context or screenshots about the feature request here.

.github/pull_request_template.md

@@ -10,8 +10,6 @@ Please check if your PR fulfills the following requirements:
 doc.
 - [ ] Tests for the changes have been added (for bug fixes / features).
 - [ ] Docs have been reviewed and added / updated if needed (for bug fixes / features).
-- [ ] Build (`yarn run build`) was run locally and any changes were pushed.
-- [ ] Tests (`yarn run test`) has passed locally and any fixes were made for failures.
 
 ## Pull request type
 

.github/workflows/create-release.yml

@@ -4,7 +4,7 @@ name: Create release
 on:
   push:
     tags:
-      - 'v*'
+      - 'v*.*.*'
 
 jobs:
   create_release:

.pre-commit-config.yaml

@@ -4,17 +4,17 @@ exclude: ^\.gitleaks\.toml$
 repos:
   # Security
   - repo: https://github.com/Yelp/detect-secrets
-    rev: v1.3.0
+    rev: v1.4.0
     hooks:
       - id: detect-secrets
         stages: ["commit", "push"]
   - repo: https://github.com/zricethezav/gitleaks
-    rev: v8.13.0
+    rev: v8.15.0
     hooks:
       - id: gitleaks
         stages: ["commit", "push"]
   - repo: https://github.com/gitguardian/ggshield
-    rev: v1.13.3
+    rev: v1.13.5
     hooks:
       - id: ggshield
         language_version: python3

CONTRIBUTING.md

@@ -1,22 +1,24 @@
-<!-- markdownlint-disable-file MD013 -->
-
 # Contributing guidance
 
-We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
+We love your input! We want to make contributing to this project as easy and
+transparent as possible, whether it's:
 
 - Reporting a bug
 - Discussing the current state of the code
 - Submitting a fix
 - Proposing new features
 - Becoming a maintainer
 
-## We Develop with GitHub
+## We develop with GitHub
 
-We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
+We use GitHub to host code, to track issues and feature requests, as well as
+accept pull requests.
 
-## We Use [GitHub Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
+## We use GitHub flow, so all code changes happen through pull requests
 
-Pull requests are the best way to propose changes to the codebase (we use [GitHub Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
+Pull requests are the best way to propose changes to the codebase (we use
+[GitHub flow](https://guides.github.com/introduction/flow/index.html)). We
+actively welcome your pull requests:
 
 1. Fork the repo and create your branch from `main`.
 2. If you've added code that should be tested, add tests.
@@ -27,24 +29,31 @@ Pull requests are the best way to propose changes to the codebase (we use [GitHu
 
 ## Any contributions you make will be under the MIT Software License
 
-In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
+In short, when you submit code changes, your submissions are understood to be
+under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers
+the project. Feel free to contact the maintainers if that's a concern.
 
 ## Report bugs using [GitHub Issues](https://github.com/fabasoad/pre-commit-snyk/issues)
 
-We use GitHub issues to track public bugs. Report a bug by opening a new issue. It's that easy!
+We use GitHub issues to track public bugs. Report a bug by opening a new issue.
+It's that easy!
 
 ## Create issue using provided GitHub issue templates
 
-This repository has issue templates for bug report and feature request. Please use them to create an issue and fill all required fields.
+This repository has issue templates for bug report and feature request. Please
+use them to create an issue and fill all required fields.
 
-## Use a Consistent Coding Style
+## Use a consistent coding style
 
-Please follow all the rules from [this](https://google.github.io/styleguide/shellguide.html) great guide provided by Google for coding style.
+Please follow all the rules from [this](https://google.github.io/styleguide/shellguide.html)
+great guide provided by Google for coding style.
 
 ## License
 
-By contributing, you agree that your contributions will be licensed under its MIT License.
+By contributing, you agree that your contributions will be licensed under its
+MIT License.
 
 ## References
 
-This document was adapted from the open-source contribution guidelines provided by [briandk](https://gist.github.com/briandk/3d2e8b3ec8daf5a27a62).
+This document was adapted from the open-source contribution guidelines provided
+by [briandk](https://gist.github.com/briandk/3d2e8b3ec8daf5a27a62).

README.md

@@ -1,7 +1,8 @@
 # Snyk pre-commit hooks
 
-<!-- markdownlint-disable-next-line MD013 -->
-![GitHub release](https://img.shields.io/github/v/release/fabasoad/pre-commit-snyk?include_prereleases) ![Functional Tests](https://github.com/fabasoad/pre-commit-snyk/workflows/Functional%20Tests/badge.svg) [![pre-commit.ci status](https://results.pre-commit.ci/badge/github/fabasoad/pre-commit-snyk/main.svg)](https://results.pre-commit.ci/latest/github/fabasoad/pre-commit-snyk/main)
+![GitHub release](https://img.shields.io/github/v/release/fabasoad/pre-commit-snyk?include_prereleases)
+![Functional Tests](https://github.com/fabasoad/pre-commit-snyk/workflows/Functional%20Tests/badge.svg)
+[![pre-commit.ci status](https://results.pre-commit.ci/badge/github/fabasoad/pre-commit-snyk/main.svg)](https://results.pre-commit.ci/latest/github/fabasoad/pre-commit-snyk/main)
 
 1. [snyk-container](#snyk-container)
 2. [snyk-iac](#snyk-iac)