Unfortunately, there’s no pre-rolled report for this. You’re going to have to find it (painfully) manually. What you’ll need to do is find the largest branch of each project and sum those LOC counts.
Do we have to analyze the main branch in order to see the total lines of code. Right now, I’m only seeing the New Lines.
We’ve been using SonarCloud with one repository for some time, and we’re in the process of adding four more (of various sizes). When I got to the second new project, we hit our current LOC limit, and I’m just trying to get an idea of how much of an increase we are going to need (250, 500, 1m?).
We’re using Git and so the branches are going to be roughly the same size as the default branch. If I know the default branch size, and I know how many PRs we create in a month, is it just:
(Default Branch LOC) * (PRs per Month) = Monthly LOC estimate.
I’m surprised that the billing function doesn’t indicate the total for our account someplace. Since SonarCloud knows we are exceeding the limit, you’d think we’d be able to view the current total for the month.
(P1 LOC) + (P2 LOC) + (P3 LOC) + (P4 LOC) = Total license LoC
We’re never going to do anything to incent you to analyze less frequently. We want you to get the benefit of analyzing every commit & PR, so you can’t “use up” your license by analyzing the same code base over and over.
Really, all you need to do is find the largest branch/PR for each project and sum those numbers.
Fair enough. I’ll ping the Product Manager on that.
You’ve resurrected a thread that’s more than 1.5 years old. There’s been a lot of water under the bridge - and new SonarCloud packages - since then.