renovate/test
Rhys Arkins 6e9c73e35a feat: restart repo renovate after automerge (#751)
Previously, the automerge feature was causing some undesirable behaviour when multiple branches were open at the same time. Example: #707. The main problem is that other branches will still be calculated based on the original `package.json` contents and not the post-merge contents. The simplest solution seems to be:
- Stop all subsequent branch processing after any automerge
- Restart repository renovation
This continues until no branch has automerged in a cycle.

Closes #750
2017-08-28 15:50:11 +02:00
..
_fixtures fix: migrate presets when resolving (#733) 2017-08-25 06:25:25 +02:00
api feat: support timeout for pr creation = not-pending (#748) 2017-08-28 11:37:09 +02:00
config feat: convet ignoreNodeModules to ignorePaths (#741) 2017-08-26 21:28:29 +02:00
logger feat: Pre-fetch all package.json files (#642) 2017-08-08 06:25:44 +02:00
workers feat: restart repo renovate after automerge (#751) 2017-08-28 15:50:11 +02:00
.eslintrc.js Move tests to Jest (#94) 2017-02-09 05:30:00 +01:00
chai.js Refactor config 2017-01-20 14:03:18 +01:00
renovate.spec.js Refactor config definitions and onboarding values (#360) 2017-06-26 13:08:57 +02:00