-
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
docs: describe known limitations #11946
docs: describe known limitations #11946
Conversation
I know this is a really, really rough draft! I'm trying to feel out what we need to cover, and I don't know the ins and outs of the bot.... 😉 |
Co-authored-by: Rhys Arkins <rhys@arkins.net>
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.
I'm ok to start with this and improve it over time
Okay! I don't have anything meaningful to add anyways... 😄 😉 |
🎉 This PR is included in version 27.25.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Changes:
Context:
We should set proper expectations with regards to Renovate bot's performance.
People like to imagine a super fast and powerful bot, that will do anything they can throw at it.
So we should explain what the bot can and cannot do for the user, and explain why we have some limitations.
Some things are a design decision, and other things are on our todo list.
For things that are on our todo list, we should mention issues that the reader can follow.
Inspired by discussion: #11884
Documentation (please check one with an [x])
How I've tested my work (please tick one)
I have verified these changes via: