jedcunningham commented on a change in pull request #17917:
URL: https://github.com/apache/airflow/pull/17917#discussion_r698713295



##########
File path: .github/ISSUE_TEMPLATE/airflow_helmchart_bug_report.yml
##########
@@ -0,0 +1,134 @@
+---
+name: Airflow Helm Chart Bug report
+description: Problems and issues with Apache Airflow Official Helm Chart
+labels: ["kind:bug", "area:helm-chart"]
+body:
+  - type: markdown
+    attributes:
+      # yamllint disable rule:line-length
+      value: "
+        <img 
src='https://raw.githubusercontent.com/apache/airflow/main/docs/apache-airflow/img/logos/airflow_64x64_emoji_transparent.png'
 align='left' width='120' height='120'>
+        Thank you for finding the time to report the problem!
+
+        We really appreciate the community efforts to improve Airflow.
+
+        Note that this issue is only for the
+        [Official Apache Airflow Helm 
Chart](https://airflow.apache.org/docs/helm-chart/stable/index.html).
+        If you use another 3rd-party Chart, you should report your issue in 
the repo of that chart instead.
+
+        Note, that you do not need to create an issue if you have a change 
ready to submit!
+
+        You can open [Pull Request](https://github.com/apache/airflow/pulls) 
immediately instead.
+        <br clear='left'/>"
+      # yamllint enable rule:line-length
+  - type: dropdown
+    attributes:
+      label: Official Helm Chart version
+      description: >
+        What Apache Airflow version are you using? Only Airflow 2 is supported 
for bugs. If you wish to
+        discuss Airflow 1.10, open 
[Discussion](https://github.com/apache/airflow/discussions) instead!

Review comment:
       ```suggestion
           What Apache Airflow Helm Chart version are you using?
   ```




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to