Remove #yaml tag from generic error message URL - #641
Merged
Conversation
This error isn't `yaml`-specific. Looks like this got committed (without PR?) as part of addressing jazzband#524 and perhaps bypassed PR/review.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #641 +/- ##
=======================================
Coverage 93.14% 93.14%
=======================================
Files 29 29
Lines 3226 3226
=======================================
Hits 3005 3005
Misses 221 221 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
claudep
approved these changes
May 20, 2026
claudep
left a comment
claudep
left a comment
Contributor
There was a problem hiding this comment.
Thanks for the fix, looks good!
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
3 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 error isn't
yaml-specific. Looks like this got committed (without PR?) as part of addressing #524 and perhaps bypassed PR/review: 0a3511f#diff-026edabea10cc8f56b3dc11a795a25d0bdc86ae602fc6649cd30730b5624ba78R336-L353Possible there are other related changes around this code that should be made too, but seemed like fixing the misleading error message might help a little. Here's another later related commit: b2be12e