refactor(util/yaml): allow to set failure behavior when parsing multidoc yamls #26763
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
6 tasks
viceice
reviewed
Jan 20, 2024
viceice
approved these changes
Jan 20, 2024
|
🎉 This PR is included in version 37.140.15 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
zT-1337
pushed a commit
to scm-manager/renovate
that referenced
this pull request
Jan 22, 2024
…doc yamls (renovatebot#26763) Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
zT-1337
pushed a commit
to scm-manager/renovate
that referenced
this pull request
Jan 24, 2024
…doc yamls (renovatebot#26763) Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
zT-1337
pushed a commit
to scm-manager/renovate
that referenced
this pull request
Jan 24, 2024
…doc yamls (renovatebot#26763) Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Changes
Adds a YAML option to define what should happen if a document in the file fails schema parsing
Context
This is as preperation for #26762
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: