Renovate: cannot enable renovatebot

[piotr-s-brainhub]

I have installed renovatebot but it doesn't open any PRs for my public repos.
e.g. no PR for this one https://github.com/piotr-s-brainhub/joi-router using package.json

[rarkins]

Renovate skips forked repositories by default. If you want it to run then you'll need to add a renovate.json file to the repo with "includeForks": true in its config.

[piotr-s-brainhub]

@rarkins

I managed to configure renovate for public repos but I have no idea why it doesn't open any PR for private repos. My plan should allow that and I selected exactly which private repo should have renovate enabled.

[rarkins]

This is all that's been detected for your account:

i.e. all public

[piotr-s-brainhub]

@rarkins

sorry, I have already used my free trial so @pavelbely helped me to activate for dmx-io/dmx-inventory (a private repo)

[rarkins]

It looks like it ran about 7 minutes ago

[piotr-s-brainhub]

OK, now I can see

[piotr-s-brainhub]

@rarkins

we configured renovate to work for all repos in dmx-io organization but it opened only for some of them:

• dmx-dashboard
• dmx-appraise-it
• npm-edmunds
• dmx-vehicle-info
• dmx-authentication
• dmx-api-gateway
• dmx-appraisals
• dmx-inventory
• npm-dmx-utils

but for most repos after several hours there's still no PR:

• core-microservice
• dmx-admin-2
• dmx-admin
• dmx-auctions
• dmx-cli
• dmx-data-ingestion
• dmx-grade-it
• dmx-grades
• dmx-media
• dmx-mobile
• dmx-notifications-legacy
• dmx-notifications
• dmx-payments
• dmx-reports
• dmx-scheduling
• dmx-slackbot
• dmx-webhooks
• koa-joi-router
• msvc-market-data
• npm-black-book
• npm-carfax
• npm-data-models
• npm-dmx-sdk
• npm-fca
• npm-forest-data-models
• npm-galves
• npm-grade-it-tools
• npm-kelley-blue-book
• npm-koa-qs
• npm-logform
• npm-logger
• npm-manheim
• npm-market-data
• npm-motor
• npm-winston-slack
• npm-winston
• test-helpers
• validation-schemas
• winston-loggly

So what is the maximum time to open a PR when renovate is activated or some library becomes available in a new version?
Can this time be lower after upgrading our plan to Organization Large?

[rarkins]

@piotr-s-brainhub those repositories were all in the job queue. The account dmx-io currently has no plan detected (not even a trial) so therefore jobs take the lower priority. Priority as you probably guessed goes Large -> Medium -> Small -> No plan. I bumped your jobs up to high priority manually just now so that you can see the effect.

[piotr-s-brainhub]

Thanks very much. @rarkins

[piotr-s-brainhub]

@rarkins

do you happen to know why I have ### Lock file problem - An unexpected error occurred: "https://registry.yarnpkg.com/@dmx%2fnpm-logger: Not found". at https://github.com/dmx-io/npm-black-book/pull/17 ?

I hardcoded the NPM token and it seems to work in all the microservices and some libraries in dmx-io organization but for many libraries I get Lock file problem

[rarkins]

@piotr-s-brainhub please raise an issue in the config help repo and include as much info as possible on your config and what you have observed. e.g. do private modules work on some repos and not others? for some packages but not others? etc.

That error message is generated by Yarn itself btw.

[piotr-s-brainhub]

@rarkins

I created lockfile issue in https://github.com/renovatebot/renovate/issues/3184