Rhys Arkins ac09b9d7cd feat: cache npm results in memory per-run ... We currently use got’s inbuilt caching for npmjs, however it still results in a roundtrip/304 even when cached. The when using presets is that a package like renovate-config-default gets looked up 10+ times unnecessarily. With this feature we assume that npm lookups don’t change for the duration of a run, and even if they did then we’d prefer the reliability of using the first lookup. Closes #1389		2018-01-15 11:53:02 +01:00
..
init	feat: cache npm results in memory per-run	2018-01-15 11:53:02 +01:00
onboarding	feat: baseBranches (multi-branch) support (#1379)	2018-01-12 07:47:18 +01:00
updates	feat: baseBranches (multi-branch) support (#1379)	2018-01-12 07:47:18 +01:00
cleanup.js	refactor: debug if repoIsOnboarded	2018-01-10 09:09:17 +01:00
configured.js	feat: return result from renovateRepository	2017-11-05 05:45:49 +01:00
error-config.js	fix: check onboarding pr when handling config error	2018-01-08 15:53:52 +01:00
error.js	fix: propagate registry-failure errors to avoid config validation warnings	2018-01-14 18:58:49 +01:00
index.js	feat: baseBranches (multi-branch) support (#1379)	2018-01-12 07:47:18 +01:00
write.js	fix: ignore onboarding branch when calculating pr hourly limit	2018-01-12 10:02:36 +01:00