Should I exclude .slconfig from version control?

0

I am using SonarLint in my .NET Core project. When I integrate projects with SonarLint, the following files are generated within the .sonarlint folder:

  • <NombreProyectoSonarQube>CSharp.ruleset
  • <NombreSolucion>.slconfig

The .ruleset file contains the rules for Sonarlint and SonarQube, so I keep this file in version control.

But what about .slconfig Should I keep this file in version control or should I exclude it? (add it to .gitignore in my case)

    
asked by Carlos Muñoz 02.11.2018 в 08:34
source

1 answer

0

This Yes file must be included in the version control.

This file controls the synchronization of the source code and SonarQube.

Includes, among other things:

  • ServerUri pointing to the SonarQube server to which the project is linked.
  • ProjectKey with the project key on the SonarQube server.
  • Profiles that includes ProfileKey which is an identifier for the Quality profile selected in the servitor.

Source: This SonarSource community publication: SonarLint source control

    
answered by 08.11.2018 / 23:05
source