Repository is a fork and not manually configured (with includeForks: true)

Question

Repository is a fork and not manually configured (with includeForks: true)

Closed this issue 4 years ago · 10 comments

This repo has includeForks set to true, however, the bot is throwing the following error in the logs & doesn't continue.

Repository is a fork and not manually configured - skipping

I can't see anywhere in the code this scenario would make sense other than if the renovate JSON was being misinterpreted.

Answer 1 · 2021-03-04T19:14:28.000Z

It seems we haven't documented this properly, because it's only supported when the file name is renovate.json

Answer 2 · 2021-03-04T19:18:21.000Z

Oh right, thanks! Can it still live in .github or does it have to go back to the root @rarkins?
Also, just out of curiosity, why does the filename matter? I thought .json5 was just treated as an alternate.

Answer 3 · 2021-03-04T19:22:30.000Z

Because when it's a fork we don't want to clone the whole repo just in case it has a config file. Instead we do a single API request to check if renovate.json returns a value and then checks if it includes the field. Therefore can't be in .github either.

The hosted app has been installed into 100,000 forks so the difference in load on GitHub is significantly less by avoiding a clone.

Answer 4 · 2021-03-04T19:24:30.000Z

Ouch, alright; that makes a lot more sense.
If I add a renovate.json into the root of the repo with the following, will it go and look for the other file?

{ "includeForks": true }

Answer 5 · 2021-03-04T19:28:19.000Z

Unfortunately I think renovate.json takes preference

Answer 6 · 2021-03-04T19:29:38.000Z

We may be able to do some git tricks to fetch just a file list or limited clone but would need research done first

Answer 7 · 2021-03-04T19:46:50.000Z

Ah, so sparse checkouts/clone filters/etc.? That'd be way better than cloning the entire repo

Answer 8 · 2021-04-12T18:30:41.000Z

I'd also be in favor of a proposal to support this behavior. In the meantime, it'd probably make sense to update this portion of the docs to reflect this behavior.

I tried looking for a docs repo but couldn't find one. If you can point me in that direction, happy to submit a PR

Answer 9 · 2021-04-12T18:43:09.000Z

Check out the docs/ folder in this repo for sources

Answer 10 · 2021-05-31T11:23:49.000Z

I'm going to archive this repository so that we have conversations in one place. Therefore please create an "App Support" discussion here if this problem or suggestion is still relevant: https://github.com/renovatebot/renovate/discussions