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
Showing
- lib/workers/branch/index.js 11 additions, 8 deletionslib/workers/branch/index.js
- lib/workers/pr/index.js 7 additions, 6 deletionslib/workers/pr/index.js
- lib/workers/repository/index.js 97 additions, 79 deletionslib/workers/repository/index.js
- test/workers/branch/index.spec.js 1 addition, 0 deletionstest/workers/branch/index.spec.js
- test/workers/repository/index.spec.js 23 additions, 1 deletiontest/workers/repository/index.spec.js
Loading
Please register or sign in to comment