michael-s-molina commented on code in PR #26375: URL: https://github.com/apache/superset/pull/26375#discussion_r1438221048
########## .github/ISSUE_TEMPLATE/bug-report.yml: ########## @@ -0,0 +1,98 @@ +name: Bug report +description: File a bug report to improve Superset's stability +labels: ["bug"] +body: + - type: textarea + id: bug-description + attributes: + label: Bug description + description: A clear and concise description of what the bug is. + validations: + required: true + - type: textarea + id: repro-steps + attributes: + label: How to reproduce the bug + placeholder: | + 1. Go to '...' + 2. Click on '....' + 3. Scroll down to '....' + 4. See error + validations: + required: true + - type: textarea + id: screenshots-recordings + attributes: + label: Screenshots/recordings + description: If applicable, add screenshots or recordings to help explain your problem. + - type: markdown + attributes: + value: | + ### Environment + + Please specify your environment. If your environment does not match the alternatives, + you need to upgrade your environment before submitting the issue as it may have already been fixed. + For additional information about the releases, check out the [release page](https://github.com/apache/superset/wiki). + - type: dropdown + id: superset-version + attributes: + label: Superset version + options: + - master + - "3.1.0" + - "3.0.3" + validations: + required: true + - type: dropdown + id: python-version + attributes: + label: Python version + options: + - "3.9" + - "3.10" + - "3.11" + - Not applicable Review Comment: It matters for Docker envs too. I think the idea here is to use the Not applicable when this information is clearly not relevant to fix the issue. It can even be a problem in Python code that has nothing to do with its version. I believe just a generic Not applicable is sufficient. We can always request that information if necessary 😉 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
