Where is the tutorial mentioned in all the docs? Says analysis will be automatic, but how?

[nutmix (john little)]

@ganncamp

There are multiple reasons for that. One is that this thread is about SonarQube Server and (as I’m aware from some of your other threads) you’re using SonarQube Cloud. The options vary. This is one feature that hasn’t made the jump from one product to the other.

You need to edit your branch pattern.

And since staging was initially created as a short-lived branch, you’ll need to delete it and re-create it after you’ve corrected the pattern. Branch types are immutable.

When you re-create it, make sure to do so without passing a branch name parameter. This means it will be created as main in SonarCloud. You can then rename it to staging.

Sorry, this is difficult to undestand.

1. the long lived branches pattern in the top right already says Long-lived branches pattern:(branch|staging|feature)-.*
2. There is no edit button to edit the branch patter. We can send a ticket to the organisation admins, but we would need to know exactly what to change it to. What should it be?
3. how do we delete staging?
4. How do we re-create it?
5. If we run the pipeline “without passing a branch name parameter” then this wont work - it completely ignores our staging branch and any PRS created on it.
6. How will it be created as main? We have only ever run the analyse command on the staging branch or a PR of it, and it took from that the main branch was master. Unless we do something different to change it, we wont get staging as the main branch