Add issue templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,70 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: 'issue title'
+labels: 'bug'
+assignees: ''
+
+---
+
+<!-- Thanks for filing an issue!
+Before hitting the button, please answer these questions.
+It's helpful to search the existing GitHub issues first.
+It's likely that another user has already reported the issue you're facing, or it's a known issue that we're already aware o. 
+
+Fill in as much of the template below as you can.
+The more information we have the better we can help you.
+
+Be ready for followup questions, and please respond in a timely manner.
+If we can't reproduce a bug or think a feature already exists, we might close your issue.
+If we're wrong, PLEASE feel free to reopen it and explain why.
+-->
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**Version of Helm and Kubernetes**:
+
+Helm Version:
+
+```console
+$ helm version
+please put the output of it here
+```
+
+Kubernetes Version:
+
+```console
+$ kubectl version
+please put the output of it here
+```
+
+
+**Which version of the chart**:
+
+
+**What happened**:
+
+
+**What you expected to happen**:
+
+
+**How to reproduce it** (as minimally and precisely as possible):
+
+<~--
+This could be something like:
+
+values.yaml (only put values which differ from the defaults)
+
+```
+key: value
+```
+
+```
+helm install my-release {{ .GitHubOrg }}/name-of-chart --version version --values values.yaml
+```
+
+-->
+
+
+**Anything else we need to know**:

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,33 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: 'issue title'
+labels: 'enhancement'
+assignees: ''
+
+---
+
+<!--
+Thanks for filing an issue!
+Before hitting the button, please answer these questions.
+It's helpful to search the existing GitHub issues first.
+It's likely that another user has already reported the issue you're facing, or it's a known issue that we're already aware of.
+
+Describe *in detail* the feature/behavior/change you'd like to see.
+
+Be ready for followup questions, and please respond in a timely manner.
+If we can't reproduce a bug or think a feature already exists, we might close your issue.
+If we're wrong, PLEASE feel free to reopen it and explain why.
+-->
+
+**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

@@ -0,0 +1,41 @@
+<!--
+Thank you for contributing!
+Before you submit this PR we'd like to make sure you are aware of our technical requirements and best practices:
+
+* https://github.com/{{ .GitHubOrg }}/helm-charts/blob/main/CONTRIBUTING.md#technical-requirements
+* https://helm.sh/docs/chart_best_practices/
+
+For a quick overview across what we will look at reviewing your PR, please read our review guidelines:
+
+* https://github.com/helm/charts/blob/master/REVIEW_GUIDELINES.md
+
+Following our best practices right from the start will accelerate the review process and help get your PR merged quicker.
+
+When updates to your PR are requested, please add new commits and do not squash the history.
+This will make it easier to identify new changes.
+The PR will be squashed anyways when it is merged.
+Thanks.
+
+For fast feedback, please @-mention maintainers that are listed in the Chart.yaml file.
+
+Please make sure you test your changes before you push them.
+Once pushed, GitHub Actions will run across your changes and do some initial checks and linting.
+These checks run very quickly.
+Please check the results.
+We would like these checks to pass before we even continue reviewing your changes.
+-->
+
+# What this PR does / why we need it
+
+# Which issue this PR fixes
+
+*(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*
+
+- fixes #
+
+# Special notes for your reviewer
+
+# Checklist
+<!-- [Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.] -->
+- [ ] [DCO](https://github.com/{{ .GitHubOrg }}/helm-charts/blob/main/CONTRIBUTING.md#sign-off-your-work) signed
+- [ ] Chart Version bumped

README.md

@@ -2,7 +2,6 @@
 
 This repository contains templates which can be used to host your own [Helm](https://helm.sh/) chart repository on GitHub.
 
-
 Hosting your own charts on GitHub has become very easy as there are many GitHub Actions which can be used to set everything up.
 
 This repository contains ready to use Github Workflows to
@@ -41,7 +40,7 @@ This is basically a summary of helm chart migrations which already took place:
 1. `stable/jenkins` to <https://github.com/jenkinsci/helm-charts>
 1. `stable/grafana` to <https://github.com/grafana/helm-charts>
    That migration was done in about a day.
-   https://github.com/grafana/helm-charts/issues/3 was used to document the executed steps.
+   <https://github.com/grafana/helm-charts/issues/3> was used to document the executed steps.
    That's helped to write this.
 
 ### Prerequisites
@@ -57,6 +56,7 @@ This is basically a summary of helm chart migrations which already took place:
   ```shell
   brew install git-filter-repo
   ```
+
 - an empty repository in GitHub where the chart should be migrated to
 
 ### Migration Steps
@@ -82,7 +82,7 @@ This is basically a summary of helm chart migrations which already took place:
    git filter-repo --path-glob 'stable/grafana/*' --path-rename stable/:charts/
    ```
 
-1. Push the repository to it's new location 
+1. Push the repository to it's new location
 
    ```shell
    git checkout -b main
@@ -153,7 +153,7 @@ This is basically a summary of helm chart migrations which already took place:
    CONTRIBUTING.md is a standard contribution template.
    That should serve as a starting point.
    If you want to enforce DCO check then [DCO](https://github.com/apps/dco) GitHub App could be used for that.
-   If you don't want DCO then also remove it from contributing guidelines. 
+   If you don't want DCO then also remove it from contributing guidelines.
 
 1. Code of Conduct
 
@@ -164,6 +164,12 @@ This is basically a summary of helm chart migrations which already took place:
    You can rename `REPO-README.md` to `README.md`.
    The file contains some placeholders, which need to be replaced.
 
+1. GitHub issue and pull request templates
+
+   - [bug report](./ISSUE_TEMPLATE/bug_report.md)
+   - [feature request](./ISSUE_TEMPLATE/feature_request.md)
+   - [pull request](./PULL_REQUEST_TEMPLATE.md)
+
 1. GitHub Workflows
 
    These are the files in `.github/workflows/`.

REPO-README.md

@@ -20,9 +20,9 @@ You can then run `helm search repo {{ .GitHubOrg }}` to see the charts.
 ## Contributing
 
 <!-- Keep full URL links to repo files because this README syncs from main to gh-pages.  -->
-We'd love to have you contribute! Please refer to our [contribution guidelines](https://github.com/{{ .GitHubOrg }}/helm-charts/blob/main/CONTRIBUTING.md) for details.
+We'd love to have you contribute! Please refer to our [contribution guidelines](<https://github.com/{{ .GitHubOrg }}/helm-charts/blob/main/CONTRIBUTING.md>) for details.
 
 ## License
 
 <!-- Keep full URL links to repo files because this README syncs from main to gh-pages.  -->
-[Apache 2.0 License](https://github.com/{{ .GitHubOrg }}/helm-charts/blob/main/LICENSE).
+[Apache 2.0 License](<https://github.com/{{ .GitHubOrg }}/helm-charts/blob/main/LICENSE>).