Hello,
In our SonarQube Cloud project, develop is the Sonar main branch and master is another long-lived branch. Both branches are regularly analyzed.
We have marked several issues as Accepted on develop. After merging develop into master and analyzing master, the corresponding issues are still open on master.
Is this expected? What process should we follow to carry these acceptance decisions from develop to master when we merge the two long-lived branches?
Hey @Oodini, as per the docs, issue status synchronization only works when merging a short-lived branch into a long-lived branch. In that case, the status is copied over to the long-lived branch.
To me, it seems like the “gitflow” type of workflow you’re using is not really what our system is designed for. I’m going to flag this for our PMs in case they have any additional insight to share or in case they want to take this into account.
Hi @andres ,
Yet it is widely used.
Most of workflows use at least 3 levels of branches (master and develop as long-lives branches, and feature branches as short-lived branches). The “official gitflow” adds a fourth level, the release branches, between develop and master.