feat: add workflow to enforce directory sorting #308
Merged
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
Member
Author
|
First CI run fails as expected, and prints a diff of the proposed changes: https://github.com/SpaceApi/directory/actions/runs/18754130264/job/53501434821 After sorting the JSON document as proposed, the CI passes: https://github.com/SpaceApi/directory/actions/runs/18754311286/job/53502087007 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
In our PR template we ask contributors to make sure that "the new entry is at the correct (alphabetically sorted) line", however we neither enforced this so far, nor did we provide a canonical sort order.
This PR attempts to fix this by adding a workflow that uses jq's sorting feature.