From 837d75b49675fc17804f451b0a945be76bedcc22 Mon Sep 17 00:00:00 2001
From: amartin <49920382+amartingarcia@users.noreply.github.com>
Date: Tue, 6 Aug 2024 10:37:57 +0200
Subject: [PATCH] feat: Remove old files (#3)

---
 .github/ISSUE_TEMPLATE/bug_report.yaml      | 88 ---------------------
 .github/ISSUE_TEMPLATE/feature_request.yaml | 40 ----------
 .github/PULL_REQUEST_TEMPLATE.md            | 32 --------
 .github/workflows/lint-test.yaml            |  4 +-
 CONTRIBUTING.md                             | 41 ----------
 5 files changed, 1 insertion(+), 204 deletions(-)
 delete mode 100644 .github/ISSUE_TEMPLATE/bug_report.yaml
 delete mode 100644 .github/ISSUE_TEMPLATE/feature_request.yaml
 delete mode 100644 .github/PULL_REQUEST_TEMPLATE.md
 delete mode 100644 CONTRIBUTING.md

diff --git a/.github/ISSUE_TEMPLATE/bug_report.yaml b/.github/ISSUE_TEMPLATE/bug_report.yaml
deleted file mode 100644
index e347bed..0000000
--- a/.github/ISSUE_TEMPLATE/bug_report.yaml
+++ /dev/null
@@ -1,88 +0,0 @@
-name: Bug report
-description: Create a bug report
-title: "[steampipe] Bug title"
-labels: [bug]
-body:
-  - type: markdown
-    attributes:
-      value: Please be cautious with the sensitive information/logs while filing the issue.
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Describe the bug a clear and concise description of what the bug is.
-    validations:
-      required: true
-
-  - type: input
-    id: helm-version
-    attributes:
-      label: What's your helm version?
-      description: Output of `#~ helm version`
-    validations:
-      required: true
-
-  - type: input
-    id: kubectl-version
-    attributes:
-      label: What's your kubectl version?
-      description: Output of `#~ kubectl version`
-    validations:
-      required: true
-
-  - type: input
-    id: chart-version
-    attributes:
-      label: Chart version
-      description: Enter the version of the chart that you encountered this bug.
-    validations:
-      required: true
-
-  - type: textarea
-    id: explain-bug
-    attributes:
-      label: Explain bug
-      description: Explain what happened.
-    validations:
-      required: false
-
-  - type: textarea
-    id: expected-result
-    attributes:
-      label: What you expected to happen?
-      description: Enter what you expected to happen.
-    validations:
-      required: false
-
-  - type: textarea
-    id: reproduce-bug
-    attributes:
-      label: How to reproduce it?
-      description: Explain step-by-step if is possible.
-    validations:
-      required: false
-
-  - type: textarea
-    id: chart-values
-    attributes:
-      label: Enter the changed values of values.yaml?
-      description: Please enter only values which differ from the defaults. Enter `NONE` if nothing's changed.
-      placeholder: "key: value"
-    validations:
-      required: false
-
-  - type: textarea
-    id: helm-command
-    attributes:
-      label: Enter the command that you execute when chart failing/misfunctioning
-      description: Enter the command as-is as how you executed.
-      placeholder: helm install [RELEASE] steampipe/steampipe --version [VERSION] -f values.yaml --debug
-    validations:
-      required: true
-
-  - type: textarea
-    id: more-info
-    attributes:
-      label: More info
-    validations:
-      required: false
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yaml b/.github/ISSUE_TEMPLATE/feature_request.yaml
deleted file mode 100644
index 7a47db8..0000000
--- a/.github/ISSUE_TEMPLATE/feature_request.yaml
+++ /dev/null
@@ -1,40 +0,0 @@
-name: Feature request
-description: Suggest an idea to improve this project
-title: "[steampipe] Feature title"
-labels: [enhancement]
-body:
-  - type: markdown
-    attributes:
-      value: Thanks for taking the time to fill out this bug report!
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Is your feature request related to a problem?
-      description: Description of what the problem is.
-    validations:
-      required: true
-
-  - type: textarea
-    id: proposals
-    attributes:
-      label: Describe the solution you'd like
-      description: Description of what you want to happen.
-    validations:
-      required: true
-
-  - type: textarea
-    id: improves
-    attributes:
-      label: Describe alternatives you've considered
-      description: Description of any alternative solutions or features you've considered. If nothing, please enter `NONE`
-    validations:
-      required: true
-
-  - type: textarea
-    id: more-info
-    attributes:
-      label: Additional context
-      description: Add any other context or screenshots about the feature request here.
-    validations:
-      required: false
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
deleted file mode 100644
index 7fd7f87..0000000
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ /dev/null
@@ -1,32 +0,0 @@
-<!--
-Before you submit this PR we'd like to make sure you are aware of our technical requirements and best practices:
-
-* https://github.com/devops-ia/helm-steampipe/blob/main/CONTRIBUTING.md#technical-requirements
-* https://helm.sh/docs/chart_best_practices/
-
-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.
-
-For fast feedback, please @-mention maintainers that are listed in the Chart.yaml file.
-
-PR Steps:
-1) Please make sure you test your changes before you push them.
-2) Once pushed, GitHub Actions will run across your changes and do some initial checks and linting.
-3) These checks run very quickly.
-4) Please check the results.
-5) 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/devops-ia/helm-steampipe/blob/main/CONTRIBUTING.md#sign-off-your-work) signed
-- [ ] Chart version bumped
diff --git a/.github/workflows/lint-test.yaml b/.github/workflows/lint-test.yaml
index 7245a93..1c2bdcd 100644
--- a/.github/workflows/lint-test.yaml
+++ b/.github/workflows/lint-test.yaml
@@ -1,8 +1,6 @@
 name: Lint and Test Charts
 
-on:
-  pull_request:
-    paths: "charts/**"
+on: pull_request
 
 jobs:
   lint-test:
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
deleted file mode 100644
index 52ad618..0000000
--- a/CONTRIBUTING.md
+++ /dev/null
@@ -1,41 +0,0 @@
-# How to contribute to Steampipe Helm Chart
-
-This document provides guidelines for contributing to the *Steampipe Helm Chart* project.
-
-## How can I contribute?
-
-### Did you find a bug?
-
-* **Ensure the bug has not already been reported** by searching on GitHub under [Issues](https://github.com/devops-ia/helm-steampipe/issues).
-* If you cannot find an open issue addressing the problem, [open a new one](https://github.com/devops-ia/helm-steampipe/issues/new). Include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the unexpected behavior.
-* Use the relevant bug report templates to create the issue, if available.
-
-### Do you intend to add a new feature or change an existing one?
-
-* Please discuss first ([open an issue](https://github.com/devops-ia/helm-steampipe/issues)) before starting any significant pull request (e.g., implementing features, refactoring code) to avoid spending time on something that might not be merged.
-* Adhere to the project's coding conventions (indentation, accurate comments, etc.) and any other requirements (such as test coverage, documentation).
-
-## Styleguides
-
-### YAML Styleguide
-
-All YAML files must adhere to the following style guide:
-
-* Indentation: Use 2 spaces for indentation.
-* No trailing spaces.
-* Use hyphens for list items.
-* Use camelCase for key names.
-* Ensure there are no syntax errors.
-
-Additional rules:
-
-* Always use double quotes for strings.
-* Keep lines to a maximum of 80 characters.
-* Ensure proper alignment of nested elements.
-
-### Git Commit Messages
-
-* Use the present tense ("Add feature" not "Added feature").
-* Use the imperative mood ("Move cursor to..." not "Moves cursor to...").
-* Limit the first line to 72 characters or less.
-* Reference issues and pull requests liberally after the first line.