Reorder OpenAPI Spec tags alphabetically #38717
Merged
Conversation
This file contains 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
|
Before - unsorted list After - ordered list |
jedcunningham
approved these changes
Apr 3, 2024
kaxil
approved these changes
Apr 3, 2024
pankajkoti
added
the
use public runners
ephraimbuddy
pushed a commit
that referenced
this pull request
Apr 4, 2024
Re-order the Tags in our API Spec view to be sorted alphabetically. This one is quick PR to fix the current order, but perhaps we could work on adding a pre-commit to ensure this list stays sorted. (cherry picked from commit 9b2d7cb)
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Re-order the Tags in our API Spec view to be sorted alphabetically.
This one is quick PR to fix the current order, but perhaps we could
work on adding a pre-commit to ensure this list stays sorted.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.