Open mnacken opened 10 months ago
@rarkins hey, any updates on this?
I believe that feature is pretty important or are there any workarounds? We have the following use case:
We have a lot of repositories in our Gitlab instance and now we're working on setting up Renovate. We think about Renovate rollout plan for product teams, so that they can easily enable it for their repositories whenever they want. I thought about running renovate on all repos, but filter them with topic "managed-by-renovate". So that whenever owners decided to onboard renovate, they just put a topic to their project and on the next run Renovate creates onboarding MR to that repo.
Thanks
@nabeelsaabna I think we need to support all the same autodiscover options in CE/EE as we have in the CLI, and we should use the same names/env.
Any possibility for a timeframe for this? This is a really annoying thing to not have :(
We are currently migrating from GitHub to GitLab. We have been using RenovateBot (formerly Renovatebot Pro, Whitesource Renovate, now Renovate CE) within a Kubernetes cluster for a long time. We appreciate the webhook functionality along with the use of a GitHub app.
We are currently faced with the question of how we want to operate the RenovateBot with our new GitLab instance (including webhook), especially since the GitHub app is not available there. Also we want to discover our projects with an GitLab Topic tag. We tried to use the autodiscoverTopics setting but that didnt work. So we did a bit of research and looked into the source code. The autodiscoverTopics feature (https://docs.renovatebot.com/self-hosted-configuration/#autodiscovertopics) seems to be reserved for the regular RenovateBot version.
It would be a great help for us if this functionality were also supported by Renovatebot CE/EE.
Best Regards, Marco