-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(datasource/custom): allow to fetch from YAML data endpoint #25695
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM ! ✅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for contributing!
Also needs prettier-fix |
🎉 This PR is included in version 37.57.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
@@ -118,6 +118,39 @@ When Renovate receives this response with the `plain` format, it will convert it | |||
|
|||
After the conversion, any `jsonata` rules defined in the `transformTemplates` section will be applied as usual to further process the JSON data. | |||
|
|||
### Yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be at h4 instead of h3 to be on the same as JSON and plain.
Line 13 misses yaml as a valid option.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
feel free to open a PR to fix it 🤗
Changes
feat(datasource/custom): allow to fetch from YAML data endpoint
Context
Closes #25634
Documentation (please check one with an [x])
How I've tested my work
I have verified these changes via: