I had a folder called “myorg.something.else” and renamed it to “MyOrg.Something.Else” by using git mv commands. Git has it recorded as a movement/rename and has preserved history.
When I pushed the branch for PR and had sonar run on it, it considered all of the files in the folder as new code, which fails the new code quality gate for several reasons.
This was existing C# code, the code in the files was not touched, only the parent folder renamed. Git history shows that this is what happened.
I shouldnt have to disable the sonar checking on my build pipelines in order to work around it.