[12.0][FIX]database_cleanup: Don't purge by default - #1978
Conversation
Modules should not be purged when completing scan without explicit user consent. Instead select modules to purge from results.
ecd2525 to
6b5fdf4
Compare
|
/ocabot merge minor |
|
/ocabot merge minor |
|
What a great day to merge this nice PR. Let's do it! |
|
This PR has the |
|
@StefanRijnhart your merge command was aborted due to failed check(s), which you can inspect on this commit of 12.0-ocabot-merge-pr-1978-by-StefanRijnhart-bump-minor. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
|
/ocabot merge minor |
|
What a great day to merge this nice PR. Let's do it! |
|
@thomaspaulb your merge command was aborted due to failed check(s), which you can inspect on this commit of 12.0-ocabot-merge-pr-1978-by-thomaspaulb-bump-minor. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
|
Yep, looks like purging modules immediately was a conscious change according to the explanation in this PR: #1316 |
|
thanks @StefanRijnhart, that's it. But by now we have the purge all button, and starting in version 14 they threw out this behavior anyways during migration. |
|
So I modified tests as per discussion above, in #2857 Closing this. |
Modules should not be purged when completing scan without
explicit user consent. Instead select modules to purge from results.
After applied fixed an issue similar to #1534