Skip to content

Supress CodeQL Warning in SPDX parsing#1444

Merged
grvillic merged 1 commit into
mainfrom
gpcastro/codeql
Jun 30, 2025
Merged

Supress CodeQL Warning in SPDX parsing#1444
grvillic merged 1 commit into
mainfrom
gpcastro/codeql

Conversation

@gpcastro

Copy link
Copy Markdown
Member

No description provided.

@gpcastro gpcastro requested a review from a team as a code owner June 30, 2025 23:11
@gpcastro gpcastro requested a review from FernandoRojo June 30, 2025 23:11
@codecov

codecov Bot commented Jun 30, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.8%. Comparing base (24b8b1b) to head (60cce77).
Report is 1 commits behind head on main.

Additional details and impacted files
@@          Coverage Diff          @@
##            main   #1444   +/-   ##
=====================================
  Coverage   89.8%   89.8%           
=====================================
  Files        414     414           
  Lines      33078   33078           
  Branches    2045    2045           
=====================================
  Hits       29732   29732           
  Misses      2934    2934           
  Partials     412     412           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@grvillic grvillic enabled auto-merge (squash) June 30, 2025 23:13
@grvillic grvillic merged commit 7389d7d into main Jun 30, 2025
24 of 25 checks passed
@grvillic grvillic deleted the gpcastro/codeql branch June 30, 2025 23:15
@github-actions

Copy link
Copy Markdown

👋 Hi! It looks like you modified some files in the Detectors folder.
You may need to bump the detector versions if any of the following scenarios apply:

  • The detector detects more or fewer components than before
  • The detector generates different parent/child graph relationships than before
  • The detector generates different devDependencies values than before

If none of the above scenarios apply, feel free to ignore this comment 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants