Qodana baseline merging during concurrent branch integration

Qodana uses a baseline file to differentiate between legacy technical debt and new regressions. When utilizing Qodana Cloud for centralized reporting, the qodana.xml file serves as the source of truth for existing issues to prevent CI failures on established code.

In a development workflow where multiple feature branches are developed concurrently, each branch may update its own baseline to account for resolved issues or accepted debt. Uncertainty arises when these divergent baselines are merged back into the main branch.

Given the current implementation of the baseline management system, how does Qodana handle the reconciliation of conflicting baseline files during a merge? Does the tool provide a mechanism to automatically merge issue signatures, or must the baseline be manually regenerated for the target branch to ensure consistency?