Repository navigation
Does closing the onboarding PR permanently opt-out of Renovate? #40605
How are you running Renovate?Self-hosted Renovate Which platform you running Renovate on?GitHub.com Which version of Renovate are you using?42.30.2 Please tell us more about your question or problemThe docs clearly explains what happens if one merges the "Configure Renovate" Pull Request and also that Renovate takes no further action for that repo until it has been merged. But it does not say what happens if one closes the PR without merging. I suspect that closing it would result in opting out of Renovate, but it's currently not mentioned in the docs. I'd be happy to contribute this to the docs, as long as someone knows the answer. 🙂 BTW: I think the mechanism of having an on-boarding PR that stalls until it's merged is very elegant. Nicely done. Logs (if relevant)n/a |
Replies: 1 comment 3 replies
|
Hi there, Someone (maybe even you) suggested the documentation should be improved. Good news, nearly all Renovate documentation is Open Source. This means you can improve the docs yourself! Please consider opening a PR to improve our documentation, instead of complaining (however subtly or politely). Even if English isn't your first language, or you're not sure what to write, please open a PR anyway. We will help you to finish the PR. You can make changes to our docs in your browser on GitHub.com. You don't need to clone any code with Git. Thanks, the Renovate |
Docs improvements always appreciated!
You can see in canonical/launchpad-retracer-operator#1 (comment) where Renovate notes that:
So you can still get a new onboarding PR created, or you can manually onboard the repo (by committing i.e.
renovate.json5)