I’ve cancelled my subscription, sorry. There’s massive potential for the product and I’d love to pay for it if/when AutoScan has the core features I need.
Analyzing other long-lived branches alongside the main branch isn’t an edge case. Here’s four other posts which outline similar needs from other users:
Hi @JC5
For clarity : Do you want your develop branch to become the main branch of your repository ?
If yes, you can rename “main” to “develop” in the “Branches and pull request” menu under Administration of your project.
HTH,
Mickaël
sonar.branch.name=devloper_1
sonar.branch.name=devloper_1
Now the default scan is still master, only a new branch is created on the sonar UI. Did not see the branch code developed
How to scan a lot of development branches (devloper_1, devloper_2, devloper_3…) every day to add new code smells, how do I do it?
E.g
master
devloper_1
devloper_2
devloper_3
devloper_4
Template for a good new topic, formatted with Markdown :
ALM used GitHub
CI system used Circle CI
Kotlin/JS
The ‘Long living branches pattern’ is not picking up the development branch -> develop|(feature|branch|release)-.*. I also tried different patterns but no effect. According to RegExr.com the regular expression should work
[12-06-2020 14-30-51]
Hi,
in my project I work 95% of the time on the develop branch. This is why I want to see develop as default in sonarcloud.io .
CI system used: Github Actions
Scanner command used when applicable: SonarSource/sonarcloud-github-action@v1.3
Languages of the repository: JavaScript
[Bildschirmfoto 2020-07-06 um 22.44.47]
However, there seems to be no option to select “develop” as main branch. The master branch shows up as master and the develop branchs as develop - which is correct - but I want…
Again, all I ask is that you add something to your backlog for it or even just discuss it with your product managers.
3 Likes