You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/08/26 15:53:59 UTC
[GitHub] [airflow] potiuk opened a new pull request #17855: Convert issue templates into forms
potiuk opened a new pull request #17855:
URL: https://github.com/apache/airflow/pull/17855
Following the discussion at
https://lists.apache.org/x/thread.html/r36d084d83cf7a66698c84185558e1bbe971c59533d4ac5d4994b0aca@%3Cdev.airflow.apache.org%3E
The issue templates are now Forms.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r696829458
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
Review comment:
I like this suggestion. I am not sure if we are there yet with people understanding the difference but on the other hand it might be a good teaching tool. We could even ask people to select the right provider from the dropdown. I will see how easy it will be to navigate with 70+ providers, but I think there is a search-as-you-type there.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-907380892
[After fixing the static check that is]
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r696806122
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for the
+ UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please makes sure you provide a reproducible step-by-step case of how to reproduce the problem.
+ As minimally and precisely as possible. Keep in mind we do not have access to your cluster or dags.
+ Rember that non-reproducible issues will be closed! Often opening a discussion is better idea!
+ - type: textarea
+ attributes:
+ label: Anything else
+ description: Anything else we need to know?
+ placeholder: >
+ How often does this problem occur? Once? Every time etc?
+ Any relevant logs to include? Put them here inside fenced
+ ``` ``` blocks or inside a foldable details tag if it's long:
+ <details><summary>x.log</summary> lots of stuff </details>
+ - type: checkboxes
+ attributes:
+ label: Are you willing to submit PR?
+ description: >
+ This is absolutely not required, but we are happy to guide you in contribution process
+ especially if you already have a good understanding of how to implement the fix.
+ Airflow is a community-managed project and we love to bring new contributors in.
+ Find us in #airflow-how-to-pr on Slack!
+ options:
+ - label: Yes I am willing to submit PR providing that I get guidance.
+ - type: checkboxes
Review comment:
But you know - I personally know a Product Manager from GitHub who once asked me "Have you seen that "n-tasks done" new feature? Do you like it? It's cool isn't it". I will ask him :)
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906732632
I think I addressed all comments. Please take a look @eladkal @leahecole @BasPH @jedcunningham @uranusjr and anyone else interested.
The change depends on #17858 - as during testing I found out some issues with pre-commits validating provider.yaml (and #17858 corrects errors resulting from it)
To make it easier to review, I squashed all the speling/etc fixes into a single commit, and added all new things in the fixup commit that follows. Those are:
* added separate doc-issue
* added separate providers issue (with multi-select list of affected providers, yay! - and also added pre-commit to verify if we have all providers there :))
* added nice preamble to explain that maybe you do not need to create the issue at all
* added some explanation to versions of airflow (main -> development, 2.1.3 - > latest released version)
* better sorting of issues in the issue list (bugs go first)
You can try it out here: https://github.com/potiuk/airflow/issues/new/choose
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906535710
You can try it here: https://github.com/potiuk/airflow/issues/new/choose - feel free to create new issues there to see how they look like!
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r696878298
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,114 @@
+---
+name: Bug report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airflow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ - "main"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airflow Providers
+ description: What Apache Airflow Providers versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What kind of deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added.
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide the context in which the problem occurred and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why you think the behaviour is erroneous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for
+ UI problems or YouTube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here.
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open a [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please make sure you provide a reproducible step-by-step case of how to reproduce the problem
+ as minimally and precisely as possible. Keep in mind we do not have access to your cluster or DAGs.
+ Rember that non-reproducible issues will be closed! Often opening a discussion is better idea!
+ - type: textarea
+ attributes:
+ label: Anything else
+ description: Anything else we need to know?
+ placeholder: >
+ How often does this problem occur? Once? Every time etc?
+ Any relevant logs to include? Put them here inside fenced
+ ``` ``` blocks or inside a foldable details tag if it's long:
+ <details><summary>x.log</summary> lots of stuff </details>
Review comment:
Agree with @uranusjr . People are used to use the markup and would be surprised.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906587308
> With Airflow being an open-to-everybody project, I'm doubting if we should have a maintainers-only form? WDYT?
I treat that one as "well maybe" and this is the best I came up with.
I often create issues which are "to dos" - especially when they are in projects and having to enter a form for those would be quite annoying (they are often neither bugs nor features). I think though that "freely" allowing users to enter issues without following the structured form is PRECISELY what I want to address with those forms. I am really annoyed by people who create a bug report, DELETE everything and override it with a free form entry.
That's why in the "maintainer only" form, I added the "checkbox" to acknowledge that you are a maintainer. Not that it will stop some people, but we then will be able to close such issues immediately with "you are not maintainer" and they will have no choice but to enter all the details in the form (or will give up which is more likely and expected).
We already have quite a number of things we can only do as maintainers acctually - most of them controlled by permissions. Mergin code, labelling issues, closing other's issues and so one. So this is nothing "extraordinary" and by no means it means that project is not "open-to-everybody".
I'd love to have it similarly done to show this form only for maintainers, but it's not currently possible. The "Confirm you are maintainer" is the next best approach I figured :).
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] jedcunningham commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
jedcunningham commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r697020759
##########
File path: .github/ISSUE_TEMPLATE/airflow_doc_issue_report.yml
##########
@@ -0,0 +1,59 @@
+---
+name: Airflow Doc issue report
+description: Problems and issues with docs of Apache Airflow
+labels: ["kind:bug", "area:docs"]
+body:
+ - type: markdown
+ attributes:
+ value: >
+ You do not need to create issue if you have a change ready to submit! You can opem
+ [Pull Request](https://github.com/apache/airflow/pulls) immediately.
Review comment:
```suggestion
You do not need to create an issue if you have a change ready to submit! You can open a
[Pull Request](https://github.com/apache/airflow/pulls) immediately.
```
##########
File path: .github/ISSUE_TEMPLATE/airflow_bug_report.yml
##########
@@ -0,0 +1,120 @@
+---
+name: Airflow Bug report
+description: Problems and issues with code of Apache Airflow core
+labels: ["kind:bug", "area:core"]
+body:
+ - type: markdown
+ attributes:
+ value: >
+ You do not need to create issue if you have a change ready to submit! You can opem
+ [Pull Request](https://github.com/apache/airflow/pulls) immediately.
Review comment:
```suggestion
You do not need to create an issue if you have a change ready to submit! You can open a
[Pull Request](https://github.com/apache/airflow/pulls) immediately.
```
##########
File path: .github/ISSUE_TEMPLATE/airflow_providers_bug_report.yml
##########
@@ -0,0 +1,193 @@
+---
+name: Airflow Providers Bug report
+description: Problems and issues with code of Apache Airflow Provider
+labels: ["kind:bug", "area:providers"]
+body:
+ - type: markdown
+ attributes:
+ value: >
+ You do not need to create issue if you have a change ready to submit! You can opem
+ [Pull Request](https://github.com/apache/airflow/pulls) immediately.
+ - type: dropdown
+ attributes:
+ label: Apache Airflow Provider
+ description: Providers that the issue report is about (you can choose more than one)
+ multiple: true
+ options:
+ - airbyte
+ - alibaba
+ - amazon
+ - apache-beam
+ - apache-cassandra
+ - apache-drill
+ - apache-druid
+ - apache-hdfs
+ - apache-hive
+ - apache-kylin
+ - apache-livy
+ - apache-pig
+ - apache-pinot
+ - apache-spark
+ - apache-sqoop
+ - asana
+ - celery
+ - cloudant
+ - cncf-kubernetes
+ - databricks
+ - datadog
+ - dingding
+ - discord
+ - docker
+ - elasticsearch
+ - exasol
+ - facebook
+ - ftp
+ - google
+ - grpc
+ - hashicorp
+ - http
+ - imap
+ - jdbc
+ - jenkins
+ - jira
+ - microsoft-azure
+ - microsoft-mssql
+ - microsoft-psrp
+ - microsoft-winrm
+ - mongo
+ - mysql
+ - neo4j
+ - odbc
+ - openfaas
+ - opsgenie
+ - oracle
+ - pagerduty
+ - papermill
+ - plexus
+ - postgres
+ - presto
+ - qubole
+ - redis
+ - salesforce
+ - samba
+ - segment
+ - sendgrid
+ - sftp
+ - singularity
+ - slack
+ - snowflake
+ - sqlite
+ - ssh
+ - tableau
+ - telegram
+ - trino
+ - vertica
+ - yandex
+ - zendesk
+ validations:
+ required: true
+ - type: dropdown
+ attributes:
+ label: Apache Airflow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest released)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ - "main (development)"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
Review comment:
```suggestion
required: true
- type: textarea
attributes:
label: Versions of Apache Airflow Providers
description: What Apache Airflow Providers versions are you using?
placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
```
We definitely want the provider version(s) here.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] github-actions[bot] commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-907445631
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r697258907
##########
File path: .github/ISSUE_TEMPLATE/airflow_providers_bug_report.yml
##########
@@ -0,0 +1,193 @@
+---
+name: Airflow Providers Bug report
+description: Problems and issues with code of Apache Airflow Provider
+labels: ["kind:bug", "area:providers"]
+body:
+ - type: markdown
+ attributes:
+ value: >
+ You do not need to create issue if you have a change ready to submit! You can opem
+ [Pull Request](https://github.com/apache/airflow/pulls) immediately.
Review comment:
Did I tell you, we have no articles in Polish :P ?
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] leahecole commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
leahecole commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r696820307
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,114 @@
+---
+name: Bug report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airflow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ - "main"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airflow Providers
+ description: What Apache Airflow Providers versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What kind of deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added.
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide the context in which the problem occurred and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why you think the behaviour is erroneous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for
+ UI problems or YouTube link to video. You can include images/screen-casts etc. by drag-dropping the
Review comment:
```suggestion
UI problems or YouTube link to a video of you demonstrating the problem. You can include files by dragging and dropping them here.
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,114 @@
+---
+name: Bug report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airflow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ - "main"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airflow Providers
+ description: What Apache Airflow Providers versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What kind of deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added.
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide the context in which the problem occurred and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why you think the behaviour is erroneous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for
+ UI problems or YouTube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here.
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open a [Discussion](https://github.com/apache/airflow/discussions) instead!
Review comment:
```suggestion
please open a [Discussion](https://github.com/apache/airflow/discussions) instead.
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,114 @@
+---
+name: Bug report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airflow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ - "main"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airflow Providers
+ description: What Apache Airflow Providers versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What kind of deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added.
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide the context in which the problem occurred and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why you think the behaviour is erroneous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for
+ UI problems or YouTube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here.
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open a [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please make sure you provide a reproducible step-by-step case of how to reproduce the problem
+ as minimally and precisely as possible. Keep in mind we do not have access to your cluster or DAGs.
+ Rember that non-reproducible issues will be closed! Often opening a discussion is better idea!
Review comment:
```suggestion
Remember that non-reproducible issues will be closed! Opening a discussion is recommended as a first step.
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,114 @@
+---
+name: Bug report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airflow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ - "main"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airflow Providers
+ description: What Apache Airflow Providers versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What kind of deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added.
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide the context in which the problem occurred and explain what happened!
Review comment:
```suggestion
Please provide the context in which the problem occurred and explain what happened
```
nit - feeling the exclamation mark is a little too much here 😁
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,114 @@
+---
+name: Bug report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airflow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ - "main"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airflow Providers
+ description: What Apache Airflow Providers versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What kind of deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added.
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide the context in which the problem occurred and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why you think the behaviour is erroneous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for
+ UI problems or YouTube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here.
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open a [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please make sure you provide a reproducible step-by-step case of how to reproduce the problem
+ as minimally and precisely as possible. Keep in mind we do not have access to your cluster or DAGs.
+ Rember that non-reproducible issues will be closed! Often opening a discussion is better idea!
+ - type: textarea
+ attributes:
+ label: Anything else
+ description: Anything else we need to know?
+ placeholder: >
+ How often does this problem occur? Once? Every time etc?
Review comment:
```suggestion
How often does this problem occur? (Once? Every time? Only when certain conditions are met?)
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,114 @@
+---
+name: Bug report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airflow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ - "main"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airflow Providers
+ description: What Apache Airflow Providers versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What kind of deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added.
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide the context in which the problem occurred and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why you think the behaviour is erroneous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for
+ UI problems or YouTube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here.
Review comment:
```suggestion
```
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906590824
> This was also my instinct - I feel like as part of a triage process, we should be able to convert issues to a Meta issue after the fact or to a label.
See my reasoning above @leahecole . I am not super-strong about it, but this is the best balance I found between "easy way to add meta features/tasks" by maintainers and "difficult to enter legitmate issue without providing all the necessary details" by contributors.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] jedcunningham commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
jedcunningham commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r697021592
##########
File path: .github/ISSUE_TEMPLATE/airflow_providers_bug_report.yml
##########
@@ -0,0 +1,193 @@
+---
+name: Airflow Providers Bug report
+description: Problems and issues with code of Apache Airflow Provider
+labels: ["kind:bug", "area:providers"]
+body:
+ - type: markdown
+ attributes:
+ value: >
+ You do not need to create issue if you have a change ready to submit! You can opem
+ [Pull Request](https://github.com/apache/airflow/pulls) immediately.
Review comment:
```suggestion
You do not need to create an issue if you have a change ready to submit! You can open a
[Pull Request](https://github.com/apache/airflow/pulls) immediately.
```
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk merged pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk merged pull request #17855:
URL: https://github.com/apache/airflow/pull/17855
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-907444982
Rebuilding to check latest constraint works after celery 5 merge.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-907379670
I am going to merge it as is, and we can always make corrections later :D
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r697256731
##########
File path: .github/ISSUE_TEMPLATE/airflow_providers_bug_report.yml
##########
@@ -0,0 +1,193 @@
+---
+name: Airflow Providers Bug report
+description: Problems and issues with code of Apache Airflow Provider
+labels: ["kind:bug", "area:providers"]
+body:
+ - type: markdown
+ attributes:
+ value: >
+ You do not need to create issue if you have a change ready to submit! You can opem
+ [Pull Request](https://github.com/apache/airflow/pulls) immediately.
+ - type: dropdown
+ attributes:
+ label: Apache Airflow Provider
+ description: Providers that the issue report is about (you can choose more than one)
+ multiple: true
+ options:
+ - airbyte
+ - alibaba
+ - amazon
+ - apache-beam
+ - apache-cassandra
+ - apache-drill
+ - apache-druid
+ - apache-hdfs
+ - apache-hive
+ - apache-kylin
+ - apache-livy
+ - apache-pig
+ - apache-pinot
+ - apache-spark
+ - apache-sqoop
+ - asana
+ - celery
+ - cloudant
+ - cncf-kubernetes
+ - databricks
+ - datadog
+ - dingding
+ - discord
+ - docker
+ - elasticsearch
+ - exasol
+ - facebook
+ - ftp
+ - google
+ - grpc
+ - hashicorp
+ - http
+ - imap
+ - jdbc
+ - jenkins
+ - jira
+ - microsoft-azure
+ - microsoft-mssql
+ - microsoft-psrp
+ - microsoft-winrm
+ - mongo
+ - mysql
+ - neo4j
+ - odbc
+ - openfaas
+ - opsgenie
+ - oracle
+ - pagerduty
+ - papermill
+ - plexus
+ - postgres
+ - presto
+ - qubole
+ - redis
+ - salesforce
+ - samba
+ - segment
+ - sendgrid
+ - sftp
+ - singularity
+ - slack
+ - snowflake
+ - sqlite
+ - ssh
+ - tableau
+ - telegram
+ - trino
+ - vertica
+ - yandex
+ - zendesk
+ validations:
+ required: true
+ - type: dropdown
+ attributes:
+ label: Apache Airflow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest released)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ - "main (development)"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
Review comment:
Right :)
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906733551
And @eladkal -> labels are set properly to doc/core/provider kind of issues. Should help with triaging :)
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-907057868
The latest fixup contains last round of grammar/content reviews. I think we are close to a "mergable" status on that one.
I thought hat we might want to be more "welcoming" and "airflow-y" in the issues and here is what I came up with:
Any more comments? Again - you can play with the latest version here: https://github.com/potiuk/airflow/issues/new/choose
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] eladkal commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
eladkal commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r696804731
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
Review comment:
Can/should we have different form for bug/feature requests related to providers?
For example in providers we care also about the provider version as well as the Airflow version.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] eladkal commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
eladkal commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r696812767
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,114 @@
+---
+name: Bug report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airflow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ - "main"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airflow Providers
+ description: What Apache Airflow Providers versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What kind of deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added.
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide the context in which the problem occurred and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why you think the behaviour is erroneous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for
+ UI problems or YouTube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here.
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open a [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please make sure you provide a reproducible step-by-step case of how to reproduce the problem
+ as minimally and precisely as possible. Keep in mind we do not have access to your cluster or DAGs.
+ Rember that non-reproducible issues will be closed! Often opening a discussion is better idea!
+ - type: textarea
+ attributes:
+ label: Anything else
+ description: Anything else we need to know?
+ placeholder: >
+ How often does this problem occur? Once? Every time etc?
+ Any relevant logs to include? Put them here inside fenced
+ ``` ``` blocks or inside a foldable details tag if it's long:
+ <details><summary>x.log</summary> lots of stuff </details>
Review comment:
maybe we can have optional designated field for log/traceback with `render: shell`? it should automatically format it no need for backticks
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906587308
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] jedcunningham commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
jedcunningham commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r696771870
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,111 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow Version
+ description: What Apache Airflow version are you using?
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for the
+ UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here
Review comment:
```suggestion
Please explain why you think the behaviour is erroneous. It is extremely helpful if you copy&paste
the fragment of logs showing the exact error messages or wrong behaviour and screenshots for
UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
image here.
```
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
uranusjr commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r696822529
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,114 @@
+---
+name: Bug report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airflow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ - "main"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airflow Providers
+ description: What Apache Airflow Providers versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What kind of deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added.
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide the context in which the problem occurred and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why you think the behaviour is erroneous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for
+ UI problems or YouTube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here.
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open a [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please make sure you provide a reproducible step-by-step case of how to reproduce the problem
+ as minimally and precisely as possible. Keep in mind we do not have access to your cluster or DAGs.
+ Rember that non-reproducible issues will be closed! Often opening a discussion is better idea!
+ - type: textarea
+ attributes:
+ label: Anything else
+ description: Anything else we need to know?
+ placeholder: >
+ How often does this problem occur? Once? Every time etc?
+ Any relevant logs to include? Put them here inside fenced
+ ``` ``` blocks or inside a foldable details tag if it's long:
+ <details><summary>x.log</summary> lots of stuff </details>
Review comment:
pip tried that and people tend to not know we already wrap the output in a code block and ```` ``` ```` the output themselves, resulting in broken markup. There’s not really a perfect UI for this, unfortunately, so I think the current method (telling users to wrap themselves) is better.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906596659
> Sounds like a good job for a bot 😎
Oh yeah!
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906543644
Small (but important) addition:
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] BasPH commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
BasPH commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906547138
Love it! Will review for typos, but 💯 for this change!
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk closed pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk closed pull request #17855:
URL: https://github.com/apache/airflow/pull/17855
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] BasPH commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
BasPH commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906565053
With Airflow being an open-to-everybody project, I'm doubting if we should have a maintainers-only form? WDYT?
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r696796809
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for the
+ UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please makes sure you provide a reproducible step-by-step case of how to reproduce the problem.
+ As minimally and precisely as possible. Keep in mind we do not have access to your cluster or dags.
+ Rember that non-reproducible issues will be closed! Often opening a discussion is better idea!
+ - type: textarea
+ attributes:
+ label: Anything else
+ description: Anything else we need to know?
+ placeholder: >
+ How often does this problem occur? Once? Every time etc?
+ Any relevant logs to include? Put them here inside fenced
+ ``` ``` blocks or inside a foldable details tag if it's long:
+ <details><summary>x.log</summary> lots of stuff </details>
+ - type: checkboxes
+ attributes:
+ label: Are you willing to submit PR?
+ description: >
+ This is absolutely not required, but we are happy to guide you in contribution process
+ especially if you already have a good understanding of how to implement the fix.
+ Airflow is a community-managed project and we love to bring new contributors in.
+ Find us in #airflow-how-to-pr on Slack!
+ options:
+ - label: Yes I am willing to submit PR providing that I get guidance.
+ - type: checkboxes
Review comment:
Not that I am aware of. I was looking for it too, but Actually, you know "issue without the willigness to fix it, is kinda incomplete :)" ... I will look for a way to disable it.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] leahecole commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
leahecole commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906583737
> With Airflow being an open-to-everybody project, I'm doubting if we should have a maintainers-only form? WDYT?
This was also my instinct - I feel like as part of a triage process, we should be able to convert issues to a Meta issue after the fact or to a label.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906550081
> Love it! Will review for typos, but 💯 for this change!
Oh yeah. I really hope it's gone bring the quality of the issues we got up and their number down.
But you never know. The users are creative :D
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] eladkal commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
eladkal commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r697301827
##########
File path: .github/ISSUE_TEMPLATE/feature_request.yml
##########
@@ -0,0 +1,58 @@
+---
+name: Airflow feature request
+description: Suggest an idea for this project or its docs
Review comment:
```suggestion
description: Suggest an idea for this project
```
the docs split out to `Airflow Doc issue report`
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906588938
> I wonder also if we should have a simpler form for reporting documentation issues?
Great Idea! will add one.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] eladkal commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
eladkal commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906596420
> Not that it will stop some people, but we then will be able to close such issues immediately with "you are not maintainer"
Sounds like a good job for a bot :sunglasses:
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r696826853
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for the
+ UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please makes sure you provide a reproducible step-by-step case of how to reproduce the problem.
+ As minimally and precisely as possible. Keep in mind we do not have access to your cluster or dags.
+ Rember that non-reproducible issues will be closed! Often opening a discussion is better idea!
+ - type: textarea
+ attributes:
+ label: Anything else
+ description: Anything else we need to know?
+ placeholder: >
+ How often does this problem occur? Once? Every time etc?
+ Any relevant logs to include? Put them here inside fenced
+ ``` ``` blocks or inside a foldable details tag if it's long:
+ <details><summary>x.log</summary> lots of stuff </details>
+ - type: checkboxes
+ attributes:
+ label: Are you willing to submit PR?
+ description: >
+ This is absolutely not required, but we are happy to guide you in contribution process
+ especially if you already have a good understanding of how to implement the fix.
+ Airflow is a community-managed project and we love to bring new contributors in.
+ Find us in #airflow-how-to-pr on Slack!
+ options:
+ - label: Yes I am willing to submit PR providing that I get guidance.
+ - type: checkboxes
Review comment:
I pinged my friend from GitHub. Let's see what he says.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906591435
> Also, should we note in all forms that if you have a code change ready to PR, there is no need to open an issue first.
Good point. I will add it!
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r696809929
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for the
+ UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please makes sure you provide a reproducible step-by-step case of how to reproduce the problem.
+ As minimally and precisely as possible. Keep in mind we do not have access to your cluster or dags.
+ Rember that non-reproducible issues will be closed! Often opening a discussion is better idea!
+ - type: textarea
+ attributes:
+ label: Anything else
+ description: Anything else we need to know?
+ placeholder: >
+ How often does this problem occur? Once? Every time etc?
+ Any relevant logs to include? Put them here inside fenced
+ ``` ``` blocks or inside a foldable details tag if it's long:
+ <details><summary>x.log</summary> lots of stuff </details>
+ - type: checkboxes
+ attributes:
+ label: Are you willing to submit PR?
+ description: >
+ This is absolutely not required, but we are happy to guide you in contribution process
+ especially if you already have a good understanding of how to implement the fix.
+ Airflow is a community-managed project and we love to bring new contributors in.
+ Find us in #airflow-how-to-pr on Slack!
+ options:
+ - label: Yes I am willing to submit PR providing that I get guidance.
+ - type: checkboxes
Review comment:
Seems it's not there (yet), but highly requested feature (for similar reasons):
* https://github.com/github/feedback/discussions/5238
* https://github.com/github/feedback/discussions/5197
* https://github.com/github/feedback/discussions/5214
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] BasPH commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
BasPH commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r696779916
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
Review comment:
```suggestion
label: Versions of Apache Airflow Providers
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for the
+ UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please makes sure you provide a reproducible step-by-step case of how to reproduce the problem.
+ As minimally and precisely as possible. Keep in mind we do not have access to your cluster or dags.
+ Rember that non-reproducible issues will be closed! Often opening a discussion is better idea!
+ - type: textarea
+ attributes:
+ label: Anything else
+ description: Anything else we need to know?
+ placeholder: >
+ How often does this problem occur? Once? Every time etc?
+ Any relevant logs to include? Put them here inside fenced
+ ``` ``` blocks or inside a foldable details tag if it's long:
+ <details><summary>x.log</summary> lots of stuff </details>
+ - type: checkboxes
+ attributes:
+ label: Are you willing to submit PR?
+ description: >
+ This is absolutely not required, but we are happy to guide you in contribution process
+ especially if you already have a good understanding of how to implement the fix.
Review comment:
```suggestion
This is absolutely not required, but we are happy to guide you in the contribution process
especially if you already have a good understanding of how to implement the fix.
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for the
+ UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
Review comment:
```suggestion
UI problems or YouTube link to video. You can include images/screen-casts etc. by drag-dropping the
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for the
+ UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please makes sure you provide a reproducible step-by-step case of how to reproduce the problem.
+ As minimally and precisely as possible. Keep in mind we do not have access to your cluster or dags.
Review comment:
```suggestion
Please make sure you provide a reproducible step-by-step case of how to reproduce the problem
as minimally and precisely as possible. Keep in mind we do not have access to your cluster or DAGs.
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
Review comment:
```suggestion
description: What Apache Airflow Providers versions are you using?
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
Review comment:
```suggestion
Please provide a context in which the problem occurred and explain what happened!
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
Review comment:
```suggestion
Please explain why do you think the behaviour is erroneous. It is extremely helpful if you copy & paste
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
Review comment:
```suggestion
description: What kind of deployment do you have?
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow Version
Review comment:
```suggestion
label: Apache Airflow version
```
##########
File path: .github/ISSUE_TEMPLATE/feature_request.yml
##########
@@ -0,0 +1,43 @@
+---
+name: Feature request
+description: Suggest an idea for this project or its docs
+labels: ["kind:feature"]
+body:
+ - type: textarea
+ attributes:
+ label: Description
+ description: A short description of your feature
+ - type: textarea
+ attributes:
+ label: Use case/motivation
+ description: What do you want to happen?
+ placeholder: >
+ Rather than telling us how you might implement this solution, try to take a
+ step back and describe what you are trying to achieve.
+ - type: textarea
+ attributes:
+ label: Related issues
+ description: Is there curently another issue asociated with this?
+ - type: checkboxes
+ attributes:
+ label: Are you willing to submit PR?
+ description: >
+ This is absolutely not required, but we are happy to guide you in contribution process
Review comment:
```suggestion
This is absolutely not required, but we are happy to guide you in the contribution process
```
##########
File path: .github/ISSUE_TEMPLATE/feature_request.yml
##########
@@ -0,0 +1,43 @@
+---
+name: Feature request
+description: Suggest an idea for this project or its docs
+labels: ["kind:feature"]
+body:
+ - type: textarea
+ attributes:
+ label: Description
+ description: A short description of your feature
+ - type: textarea
+ attributes:
+ label: Use case/motivation
+ description: What do you want to happen?
+ placeholder: >
+ Rather than telling us how you might implement this solution, try to take a
+ step back and describe what you are trying to achieve.
+ - type: textarea
+ attributes:
+ label: Related issues
+ description: Is there curently another issue asociated with this?
Review comment:
```suggestion
description: Is there currently another issue associated with this?
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
Review comment:
```suggestion
name: Bug report
```
##########
File path: .github/ISSUE_TEMPLATE/feature_request.yml
##########
@@ -0,0 +1,43 @@
+---
+name: Feature request
+description: Suggest an idea for this project or its docs
+labels: ["kind:feature"]
+body:
+ - type: textarea
+ attributes:
+ label: Description
+ description: A short description of your feature
+ - type: textarea
+ attributes:
+ label: Use case/motivation
+ description: What do you want to happen?
+ placeholder: >
+ Rather than telling us how you might implement this solution, try to take a
+ step back and describe what you are trying to achieve.
+ - type: textarea
+ attributes:
+ label: Related issues
+ description: Is there curently another issue asociated with this?
+ - type: checkboxes
+ attributes:
+ label: Are you willing to submit PR?
+ description: >
+ This is absolutely not required, but we are happy to guide you in contribution process
+ especially if you already have a good understanding of how to implement the fix.
Review comment:
```suggestion
especially if you already have a good understanding of how to implement the feature.
```
##########
File path: .github/ISSUE_TEMPLATE/feature_request.yml
##########
@@ -0,0 +1,43 @@
+---
+name: Feature request
+description: Suggest an idea for this project or its docs
+labels: ["kind:feature"]
+body:
+ - type: textarea
+ attributes:
+ label: Description
+ description: A short description of your feature
+ - type: textarea
+ attributes:
+ label: Use case/motivation
+ description: What do you want to happen?
+ placeholder: >
+ Rather than telling us how you might implement this solution, try to take a
+ step back and describe what you are trying to achieve.
+ - type: textarea
+ attributes:
+ label: Related issues
+ description: Is there curently another issue asociated with this?
+ - type: checkboxes
+ attributes:
+ label: Are you willing to submit PR?
Review comment:
```suggestion
label: Are you willing to submit a PR?
```
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] jedcunningham commented on a change in pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
jedcunningham commented on a change in pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#discussion_r696767110
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,111 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow Version
+ description: What Apache Airflow version are you using?
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
Review comment:
Should we have a "main" option too?
```suggestion
- "2.0.0"
- "main"
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,111 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow Version
+ description: What Apache Airflow version are you using?
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
Review comment:
```suggestion
software (docker-compose, helm, k8s, etc.), any customisation and configuration you added.
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,111 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow Version
+ description: What Apache Airflow version are you using?
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for the
+ UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here
Review comment:
```suggestion
Please explain why you think the behaviour is erroneous. It is extremely helpful if you copy&paste
the fragment of logs showing the exact error messages or wrong behaviour and screenshots for
UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
images here.
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,111 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow Version
+ description: What Apache Airflow version are you using?
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
Review comment:
```suggestion
Please provide the context in which the problem occurred and explain what happened!
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,111 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow Version
+ description: What Apache Airflow version are you using?
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for the
+ UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open [Discussion](https://github.com/apache/airflow/discussions) instead!
Review comment:
```suggestion
please open a [Discussion](https://github.com/apache/airflow/discussions) instead!
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for the
+ UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please makes sure you provide a reproducible step-by-step case of how to reproduce the problem.
+ As minimally and precisely as possible. Keep in mind we do not have access to your cluster or dags.
+ Rember that non-reproducible issues will be closed! Often opening a discussion is better idea!
+ - type: textarea
+ attributes:
+ label: Anything else
+ description: Anything else we need to know?
+ placeholder: >
+ How often does this problem occur? Once? Every time etc?
+ Any relevant logs to include? Put them here inside fenced
+ ``` ``` blocks or inside a foldable details tag if it's long:
+ <details><summary>x.log</summary> lots of stuff </details>
+ - type: checkboxes
+ attributes:
+ label: Are you willing to submit PR?
+ description: >
+ This is absolutely not required, but we are happy to guide you in contribution process
+ especially if you already have a good understanding of how to implement the fix.
+ Airflow is a community-managed project and we love to bring new contributors in.
+ Find us in #airflow-how-to-pr on Slack!
+ options:
+ - label: Yes I am willing to submit PR providing that I get guidance.
+ - type: checkboxes
Review comment:
It's too bad these checkboxes show up as tasks. I haven't looked, but is there any way we can avoid that?
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for the
+ UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please makes sure you provide a reproducible step-by-step case of how to reproduce the problem.
+ As minimally and precisely as possible. Keep in mind we do not have access to your cluster or dags.
+ Rember that non-reproducible issues will be closed! Often opening a discussion is better idea!
Review comment:
```suggestion
Please make sure you provide step-by-step instructions to reproduce the problem, as minimally
and precisely as possible. Keep in mind we do not have access to your cluster or dags.
Remember that non-reproducible issues will be closed! Often opening a discussion is better idea!
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for the
+ UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please makes sure you provide a reproducible step-by-step case of how to reproduce the problem.
+ As minimally and precisely as possible. Keep in mind we do not have access to your cluster or dags.
+ Rember that non-reproducible issues will be closed! Often opening a discussion is better idea!
+ - type: textarea
+ attributes:
+ label: Anything else
+ description: Anything else we need to know?
+ placeholder: >
+ How often does this problem occur? Once? Every time etc?
+ Any relevant logs to include? Put them here inside fenced
+ ``` ``` blocks or inside a foldable details tag if it's long:
+ <details><summary>x.log</summary> lots of stuff </details>
+ - type: checkboxes
+ attributes:
+ label: Are you willing to submit PR?
+ description: >
+ This is absolutely not required, but we are happy to guide you in contribution process
Review comment:
```suggestion
This is absolutely not required, but we are happy to guide you in the contribution process
```
##########
File path: .github/ISSUE_TEMPLATE/bug_report.yml
##########
@@ -0,0 +1,113 @@
+---
+name: Bug Report
+description: Problems and issues with code or docs
+labels: ["kind:bug"]
+body:
+ - type: dropdown
+ attributes:
+ label: Apache Airlfow 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!
+ multiple: false
+ options:
+ - "2.1.3 (latest)"
+ - "2.1.2"
+ - "2.1.1"
+ - "2.1.0"
+ - "2.0.2"
+ - "2.0.1"
+ - "2.0.0"
+ validations:
+ required: true
+ - type: input
+ attributes:
+ label: Operating System
+ description: What Operating System are you using?
+ placeholder: "You can get it via `cat /etc/os-release` for example"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Versions of Apache Airlfow Providers
+ description: What Apache Airflow Provders versions are you using?
+ placeholder: You can use `pip freeze | grep apache-airflow-providers` (you can leave only relevant ones)
+ - type: dropdown
+ attributes:
+ label: Deployment
+ description: What Kind of Deployment do you have?
+ multiple: false
+ options:
+ - "Managed Services (Astronomer, Composer, MWAA etc.)"
+ - "Official Apache Airflow Helm Chart"
+ - "Other 3rd-party Helm chart"
+ - "Docker-Compose"
+ - "Other Docker-based deployment"
+ - "Virtualenv installation"
+ - "Other"
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Deployment details
+ description: Additional description of your deployment.
+ placeholder: >
+ Enter any relevant details of your deployment. Especially version of your tools,
+ software (docker-compose, helm, k8s, etc.), any customisation and configuration you added
+ - type: textarea
+ attributes:
+ label: What happened
+ description: Describe what happened.
+ placeholder: >
+ Please provide a context in which the problem occured and explain what happened!
+ - type: textarea
+ attributes:
+ label: What you expected to happen
+ description: What do you think went wrong?
+ placeholder: >
+ Please explain why do you think the behaviour is erronous. It is extremely helpful if you copy&paste
+ the fragment of logs showing the exact error messages or wrong behaviour and screenshots for the
+ UI problems or youtube link to video. You can include images/screen-casts etc. by drag-dropping the
+ image here
+ - type: textarea
+ attributes:
+ label: How to reproduce
+ description: >
+ What should we do to reproduce the problem? If you are not able to provide a reproducible case,
+ please open [Discussion](https://github.com/apache/airflow/discussions) instead!
+ placeholder: >
+ Please makes sure you provide a reproducible step-by-step case of how to reproduce the problem.
+ As minimally and precisely as possible. Keep in mind we do not have access to your cluster or dags.
+ Rember that non-reproducible issues will be closed! Often opening a discussion is better idea!
+ - type: textarea
+ attributes:
+ label: Anything else
+ description: Anything else we need to know?
+ placeholder: >
+ How often does this problem occur? Once? Every time etc?
+ Any relevant logs to include? Put them here inside fenced
+ ``` ``` blocks or inside a foldable details tag if it's long:
+ <details><summary>x.log</summary> lots of stuff </details>
+ - type: checkboxes
+ attributes:
+ label: Are you willing to submit PR?
+ description: >
+ This is absolutely not required, but we are happy to guide you in contribution process
+ especially if you already have a good understanding of how to implement the fix.
+ Airflow is a community-managed project and we love to bring new contributors in.
+ Find us in #airflow-how-to-pr on Slack!
+ options:
+ - label: Yes I am willing to submit PR providing that I get guidance.
Review comment:
```suggestion
- label: Yes I am willing to submit a PR!
```
I like this better, but 🤷♂️
##########
File path: .github/ISSUE_TEMPLATE/feature_request.yml
##########
@@ -0,0 +1,43 @@
+---
+name: Feature request
+description: Suggest an idea for this project or its docs
+labels: ["kind:feature"]
+body:
+ - type: textarea
+ attributes:
+ label: Description
+ description: A short description of your feature
+ - type: textarea
+ attributes:
+ label: Use case/motivation
+ description: What do you want to happen?
+ placeholder: >
+ Rather than telling us how you might implement this solution, try to take a
+ step back and describe what you are trying to achieve.
+ - type: textarea
+ attributes:
+ label: Related issues
+ description: Is there curently another issue asociated with this?
+ - type: checkboxes
+ attributes:
+ label: Are you willing to submit PR?
+ description: >
+ This is absolutely not required, but we are happy to guide you in contribution process
+ especially if you already have a good understanding of how to implement the fix.
+ Airflow is a community-managed project and we love to bring new contributors in.
+ Find us in #airflow-how-to-pr on Slack!
+ options:
+ - label: Yes I am willing to submit PR providing that I get guidance.
Review comment:
```suggestion
- label: Yes I am willing to submit a PR!
```
##########
File path: .github/ISSUE_TEMPLATE/feature_request.yml
##########
@@ -0,0 +1,43 @@
+---
+name: Feature request
+description: Suggest an idea for this project or its docs
+labels: ["kind:feature"]
+body:
+ - type: textarea
+ attributes:
+ label: Description
+ description: A short description of your feature
+ - type: textarea
+ attributes:
+ label: Use case/motivation
+ description: What do you want to happen?
+ placeholder: >
+ Rather than telling us how you might implement this solution, try to take a
Review comment:
```suggestion
Rather than telling us how you might implement this feature, try to take a
```
##########
File path: .github/ISSUE_TEMPLATE/feature_request.yml
##########
@@ -0,0 +1,43 @@
+---
+name: Feature request
+description: Suggest an idea for this project or its docs
+labels: ["kind:feature"]
+body:
+ - type: textarea
+ attributes:
+ label: Description
+ description: A short description of your feature
+ - type: textarea
+ attributes:
+ label: Use case/motivation
+ description: What do you want to happen?
+ placeholder: >
+ Rather than telling us how you might implement this solution, try to take a
+ step back and describe what you are trying to achieve.
+ - type: textarea
+ attributes:
+ label: Related issues
+ description: Is there curently another issue asociated with this?
+ - type: checkboxes
+ attributes:
+ label: Are you willing to submit PR?
+ description: >
+ This is absolutely not required, but we are happy to guide you in contribution process
Review comment:
```suggestion
This is absolutely not required, but we are happy to guide you in the contribution process
```
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906539707
Screenshots for those who are afraid to create new issues :)
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on pull request #17855: Convert issue templates into forms
Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #17855:
URL: https://github.com/apache/airflow/pull/17855#issuecomment-906587308
> With Airflow being an open-to-everybody project, I'm doubting if we should have a maintainers-only form? WDYT?
treat that one as "well maybe" and this is the best I came up with.
I often create issues which are "to dos" - especially when they are in projects and having to enter a form for those would be quite annoying (they are often neither bugs nor features). I think though that "freely" allowing users to enter issues without following the structured form is PRECISELY what I want to address with those forms. I am really annoyed by people who create a bug report, DELETE everything and override it with a free form entry.
That's why in the "maintainer only" form, I added the "checkbox" to acknowledge that you are a maintainer. Not that it will stop some people, but we then will be able to close such issues immediately with "you are not maintainer" and they will have no choice but to enter all the details in the form (or will give up which is more likely and expected).
We already have quite a number of things we can only do as maintainers acctually - most of them controlled by permissions. Mergin code, labelling issues, closing other's issues and so one. So this is nothing "extraordinary" and by no means it means that project is not "open-to-everybody".
I'd love to have it similarly done to show this form only for maintainers, but it's not currently possible. The "Confirm you are maintainer" is the next best approach I figured :).
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org