feat: add renovateFork option
99% of the time we should not Renovate forked repositories. Previously, we skipped onboarding them unless a renovate.json was present. However, that meant that if someone forked a repository where the source was using Renovate, then the fork gets renovated automatically too. After this change, forked repositories need to set renovateFork=true in their renovate.json Closes #940 BREAKING CHANGE: Forked repositories now need to configure renovateFork=true in renovate.json
Showing
- docs/configuration.md 8 additions, 0 deletionsdocs/configuration.md
- lib/config/definitions.js 7 additions, 0 deletionslib/config/definitions.js
- lib/workers/repository/index.js 1 addition, 1 deletionlib/workers/repository/index.js
- test/workers/repository/index.spec.js 1 addition, 1 deletiontest/workers/repository/index.spec.js
Loading
Please register or sign in to comment