🤖 Fix invalid UUIDs#1928
Merged
Merged
Conversation
This commit regenerates each UUID that also existed elsewhere on Exercism. Every UUID should be unique Exercism-wide. A track can generate a suitable UUID by running `configlet uuid`.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This PR regenerates each UUID on the track that was invalid.
To be valid, each value of a
uuidkey must:canonical textual representation [1]
A track can generate a suitable UUID by running
configlet uuid.In the future,
configlet lintwill produce an error for an invalidUUID.
[1] That is, it must match this regular expression:
Tracking
exercism/v3-launch#29