jarvisfriends / inspector / 30176106897
72%
main: 72%

LAST BUILD BRANCH: openssf-quality
DEFAULT BRANCH: main
Ran
Jobs 1
Files 7
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 71.586%. Remained the same
30176106897

Pull #18

github

amarcum 
ci: add SonarQube/SonarCloud CI-based scan (SONAR_TOKEN)

Adds a pinned SonarQube scan workflow plus sonar-project.properties.
Deviates from the pasted snippet in three ways:
- branch corrected to `main` (this repo's default is main, not master)
- actions/checkout pinned to the same v7 SHA already used everywhere else
  in this repo's CI, instead of the older v4.3.1 from Sonar's generic docs
- sonar-project.properties projectKey corrected to match this repo's
  actual, already-connected SonarCloud project (the pasted value,
  jarvisfriends_open-source-sonar, was SonarCloud's placeholder text for
  creating a brand new project and would have pointed 3 repos at one
  shared analysis project)

Also wires sonar.go.coverage.reportPaths to the coverage.out this repo's
CI already produces, and runs tests in the job so that file exists.

NOTE (read before merging): this project already has SonarCloud
"Automatic Analysis" enabled (zero-config GitHub App integration — the
existing "SonarCloud Code Analysis" PR check is it). SonarCloud does not
allow Automatic Analysis and CI-based analysis on the same project at
once; the new scan will likely be rejected until Automatic Analysis is
turned off for this project (Administration > Analysis Method on
sonarcloud.io). That toggle can only be done in the SonarCloud UI.

Signed-off-by: Alex <amarcum@gmail.com>
Pull Request #18: ci: add SonarQube/SonarCloud CI-based scan (SONAR_TOKEN)

1824 of 2548 relevant lines covered (71.59%)

2380.18 hits per line

Jobs
ID Job ID Ran Files Coverage
1 30176106897.1 7
71.59
 GitHub Action Run
Source Files on build 30176106897