Update AI question header to 5th-level in PR template and add separator #60531
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The 2nd-level header is a bit too prominent - the 5th level looks way better - and separator makes it more visible that this is an extra thing added additionally to the description of the PR rather than part of the description itself.
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-1-test
Member
Author
|
This is how it looks like: 
|
Member
Author
|
Compare it with: 
|
o-nikolas
approved these changes
Jan 14, 2026
Contributor
|
And by the way, it had bothered my as well but my days are currently so long that I had no spare time raising some PRs :-D |
github-actions bot
pushed a commit
that referenced
this pull request
Jan 14, 2026
… add separator (#60531) The 2nd-level header is a bit too prominent - the 5th level looks way better - and separator makes it more visible that this is an extra thing added additionally to the description of the PR rather than part of the description itself. (cherry picked from commit e061647) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Backport successfully created: v3-1-test
|
jscheffl
pushed a commit
that referenced
this pull request
Jan 14, 2026
… add separator (#60531) (#60556) The 2nd-level header is a bit too prominent - the 5th level looks way better - and separator makes it more visible that this is an extra thing added additionally to the description of the PR rather than part of the description itself. (cherry picked from commit e061647) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Member
|
Ha, seems like we all had the same reaction after seeing it a bit more 🍻 |
ephraimbuddy
pushed a commit
that referenced
this pull request
Jan 16, 2026
… add separator (#60531) (#60556) The 2nd-level header is a bit too prominent - the 5th level looks way better - and separator makes it more visible that this is an extra thing added additionally to the description of the PR rather than part of the description itself. (cherry picked from commit e061647) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
jason810496
pushed a commit
to jason810496/airflow
that referenced
this pull request
Jan 22, 2026
…or (apache#60531) The 2nd-level header is a bit too prominent - the 5th level looks way better - and separator makes it more visible that this is an extra thing added additionally to the description of the PR rather than part of the description itself.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The 2nd-level header is a bit too prominent - the 5th level looks way better - and separator makes it more visible that this is an extra thing added additionally to the description of the PR rather than part of the description itself.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.