Fix buggy sed (wasn't picking up message) - just dump the whole json …#325
Merged
JedMeister merged 1 commit intoturnkeylinux:18.xfrom Aug 15, 2025
Merged
Conversation
OnGle
approved these changes
Aug 13, 2025
Member
OnGle
left a comment
OnGle
left a comment
There was a problem hiding this comment.
Nice, perfectly reasonable solution
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.
Just hit the GH API limit (unauthenticated) and was struggling to work out what was going on!
Turns out the sed string was buggy... I was going to fix it, then thought why? It's a dev tool so best to just dump the json and be done with it...