While this makes sense and it’s good to know, it will complicate our process.
Merges to the equivalent of Develop happen multiple times a day and developers understandably don’t want to merge or rebase work in progress multiple times a day to keep up with that.
Most of our developers don’t rebase prior to merge. This has rarely caused issues and would be a substantial process change for us. If they rebase, all reviews are dismissed, and they need to wait 40 minutes for the regression suite to run. If a new merge gets into Develop in the mean time, they’re back to square one.
Will a future version of SonarQube use the scan at the branchpoint (E) instead of the latest scan on the base branch as the reference for new issues?