Our projects within our organization has code that lives in github. For one project in particular, the primary branch used to be “master” and we renamed it to “main”. However, since the renaming, sonarqube is treating main as a short-lived branch. What we want to do is make the main branch the “main” branch in sonarqube as well. Here’s what I’ve tried to do:
Add main to the long-lived branch regex (that didn’t work)
Make main the main branch in Sonarqube via project-settings → branches & pull requests
The problem I’m running into is I can’t access project settings to get to branches and pull requests, even though I’m an organization admin/owner. This seems to be the only thing in the organization I can’t access. I’ve also tried adding my user as a project admin directly but that still did not work. What do I need to do to resolve?
For reference, this is what I’m looking for but can’t access:
Unfortunately, branch type is immutable once set. So you would have had to adjust the regex before the first analysis of main. However, presumably what you wanted was to continue the history from master to main in a single, unbroken branch. For that to work you would need to
change the regex (which you’ve done at this point)
edit the branch name in SonarQube from master to main
begin analyzing with the new branch name
Your best path forward from here is to delete your short-lived main branch (since you can’t fix it) and follow the steps above.
It’s quite possible to have org admin rights without having the ability to admin or even see an individual project.
No, I do have access to the project we’re working on. I’m also able to access the project administration. The only thing I don’t seem to have access to is the “project settings” dropdown
