-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Order bug report fields by importance #19990
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
I like it. I wonder what others think? |
|
The PR is likely ready to be merged. No tests are needed as no important environment files, nor python files were modified by it. However, committers might decide that full test matrix is needed and add the 'full tests needed' label. Then you should rebase it to the latest main or amend the last commit of the PR, and push it with --force-with-lease. |
|
I like it a lot actually :) |
|
I think I'd rather see the Airflow version still at the top, otherwise I like it as well. |
|
Good for me with Airflow version too. |
|
Looks Great to me :) |
|
@jedcunningham and others - any comments :), or shall we merge it? |

I felt the bug report form was confusing to read, because you start with some issue in mind, and first have to work through "what version", "what deployment", etc. before getting to actually reporting the bug.
This PR places "What happened", "What you expected to happen", "How to reproduce" at the top (and makes "What happened" a required field), which to me feels like a better order.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.