Closed okainov closed 3 years ago
Currently there isn't anything, but if you're going the self hosting route we could probably add an env var as a hack to support a global config, something like: DEFAULT_KODIAK_CONFIG_TOML
Could update that to check the env var and use that if set ^
Otherwise we could add a global config that is configurable via the web UI, but would be a bit more involved
Found a related issue from a while back: https://github.com/chdsbd/kodiak/issues/403
Also related - when you install the Renovate bot app on a repo, and that repo doesn't have a configuration file, renovate will open a PR with a default configuration. You can close the PR or merge it to disable/enable the bot.
We'd like to use the tool internally for ~50 different repositories and we'd prefer to configure Kodiak once on the server side and do not modify repositories. Would it be possible?