Taking config file from a branch other than repository default

[tarquin-the-brave]

The docs state that the Renovate config can be placed in a bunch of file locations on the repository's default branch. https://docs.renovatebot.com/configuration-options/

This is a bit awkward. I'm currently trialling Renovate for use in a Gitlab codebase. I've been very impressed with how non-intrusive it is (up to this point). I've been able to set up a job to run Renovate and I was impressed by its ability to autodetect dependencies.

I would like to fully proof of concept the use of Renovate on a branch, seeing what the dependency dashboard looks like, etc, but find myself needing to merge the config I want to use into the default branch. This means I can't change the config file without getting a merge request approved and going through a review process.

Maybe I've missed a CLI parameter to say "use the config file at this local path", but if I haven't, that would be a really useful feature to have.

[viceice]

nope, config needs to be on default branch, use a fork to test 😉

[TWiStErRob]

How do you fork a repository you own?

[szpak]

Just create a separate group/organization, e.g. TWiStErRob-forks.

[rarkins]

You can do a PoC without needing a config in any branch:

• Put all config in your config.js which you pass to the bot
• Include requireConfig: false and onboarding: false
• Renovate will then proceed without onboarding, and create PRs targeting the default branch

Alternatively if you want to commit a config to some other branch (e.g. foobranch):

• Configure baseBranches: ['foobranch'] in your bot config
• Add a renovate.json to foobranch manually
• Renovate will then proceed without onboarding, and create PRs targeting fooobranch

[davinkevin]

Even with it, I had to commit something to main unfortunately.

I really like renovate, but a way to work without any commit would be very good to reduce time to first result

[rarkins]

With requireConfig=optional you don't need any config/commit

[davinkevin]

Hello @rarkins,

I think I found why this behaves differently for me. Let me describe my configuration:

We have:

• a project with main as the GitHub default branch
• Our updates target the branch named release, and that one hosts the configuration we want to use, so we have "useBaseBranchConfig": "merge" and "baseBranches": ["release"] on main

In that context, I'm not able to follow steps you describe for the second part of your answer ("Alternatively if you want to commit a config to some other branch") because I can't override, from the bot config, the baseBranches parameter. I think all those useBaseBranchConfig and baseBranches cause the trouble related to my issue.

My goal is simple, I would like to open a PR to my project (commit, dedicated feature branch foobranch), but for testing purpose, I would like to run renovate bot locally (using docker or else) like if that branch was the official configuration

If you want, I can open a PR for that and we can plan a pairing session if you need to see it for real 😇.

[rarkins]

Thanks, please start a new discussion laying out your requirements first, then proposed solution

[davinkevin]

Done

[klangenk]

You can use this configuration now
https://docs.renovatebot.com/configuration-options/#usebasebranchconfig