In our repo we currently maintain multiple versions of our software, where one branch corresponds to one version.
Currently we see a lot of irrelevant issues when looking at the analysis, since all feature branches are compared to the main branch (which contains only our most recent version). Our versions differ significantly in some aspects.
How can we set the analysis so it diffs with the branch that it originated from?
E.g. if feature branch feat/512-example originates from releases/4.1, how can we make sure only new code issues are reported based on releases/4.1 and not our main branch?
Thanks in advance for the help!
Kind greetings
Benjamin
Hey @Benjamin – Currently, we only support using a single default branch as the baseline for comparing issues in pull requests. So, every feature branch gets compared to that default branch, which is configurable in settings tab of the repository from the DeepSource dashboard.
We totally get that it would be better if feature branches could be compared to the branch they actually originated from — like comparing a feature branch off of releases/4.1 to releases/4.1, instead of main. This is something we plan to support in the future, and it’s on our roadmap. We don’t have a timeline just yet.
Do you know when the timeline will be established or roughly when it could be implemented? If it takes more than a year then we might have to switch to another tool, so this info would be really helpful in our decision process.
In the meantime I’ve talked to my team and what would work for us as a workaround is to have two instances of deepsource running at the same time; one for each version. So one would have Releases/5.0 set as its default branch and the other Releases/5.1.
Now just the question: Can we run two instances of deepsource on the same organization or is it limited to one?
Hey @Benjamin – Assuming you’re on DeepSource Cloud, connecting a same organization to two instances of DeepSource is not possible. Regarding support for multiple default branches, I unfortunately don’t have a timeline for the release yet.
If you would like to consider Enterprise Server (self hosted), please e-mail me at my first name @ deepsource.io. Note that Enterprise Server would require at least 25 licenses with annual commitment. I wouldn’t recommend implementing Enterprise Server just for this workaround, as it is unnecessarily complex.