additionalBranchPrefix for customManagers

[cameronwaterman]

Tell us more.

I currently use additionalBranchPrefix to customize my branch names within packageRules blocks. I've recently added a custom manager, and discovered this configuration does not work within customManagers blocks. Requesting the additionalBranchPrefix config works for custom managers.

[cameronwaterman]

I'd also like to request the labels and automerge configuration be ported to custom managers.

Edit: And the separate major/minor configuration as well :)

[rarkins]

Sorry, but we don't want to complicate the customManagers configuration this way. packageRules is the way to achieve this. If you need to be able to distinguish between different custom managers, that will be achievable in packageRules once we add the ability to "name" each customer manager.

[cameronwaterman]

Maybe I'm not understanding then. Is it possible to specify a manager of type custom.regex within a packageRules block?

This is what my configuration currently looks like:

module.exports = {
    ...SharedConfig.commonConfig,
    enabledManagers: ['custom.regex'],
    repositories: [
        {
            repository: '<repo>',
            customManagers: [
                {
                    customType: 'regex',
                    description: <description>,
                    fileMatch: [<regex>],
                    matchStrings: [<match>],
                    depNameTemplate: '<dep-name-template>',
                    datasourceTemplate: 'docker'
                }
            ]
        }
    ]
};

Ignore the js syntax.

[rarkins]

You can

[cameronwaterman]

I got something working with a combination of packageRules and customManagers. Closing this discussion.

[pgmgb]

@cameronwaterman
We face the same issue - do you mind sharing your outcome?