-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use SonarAnalyzer.CSharp.Styling #1912
Conversation
448d733
to
943de99
Compare
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I left one non-blocking suggestion.
@@ -1,6 +1,10 @@ | |||
<?xml version="1.0" encoding="utf-8"?> | |||
<Project> | |||
<ItemGroup> | |||
<PackageReference Include="SonarAnalyzer.CSharp.Styling" Version="9.24.0.89429"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to let dependatbot/renovate do the update?
Not sure how hard it could be, but our set-script.ps1
could set the version as well to use the latest. To make things easier, we could set the version like so:
<PackageReference Include="SonarAnalyzer.CSharp.Styling" Version="9.24.0.89429"> | |
<PackageReference Include="SonarAnalyzer.CSharp.Styling" Version="9.24.0.*"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We cannot use "*" due to json lock files. Each release of sonar-dotnet would break build of all other projects.
We will let update it manually, or let renovate do the job for us.
Same as SonarSource/sonar-dotnet#9207