Skip to content

Fix Go detector Unit Tests#1429

Merged
AMaini503 merged 1 commit into
mainfrom
user/aamaini/fixut-go
Jun 10, 2025
Merged

Fix Go detector Unit Tests#1429
AMaini503 merged 1 commit into
mainfrom
user/aamaini/fixut-go

Conversation

@AMaini503

Copy link
Copy Markdown
Contributor

No description provided.

@codecov

codecov Bot commented Jun 10, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.5%. Comparing base (08a12e3) to head (1c8b6f5).
Report is 1 commits behind head on main.

Additional details and impacted files
@@          Coverage Diff          @@
##            main   #1429   +/-   ##
=====================================
  Coverage   89.5%   89.5%           
=====================================
  Files        404     404           
  Lines      31978   31977    -1     
  Branches    1994    1994           
=====================================
  Hits       28628   28628           
  Misses      2935    2935           
+ Partials     415     414    -1     

☔ 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.

@AMaini503 AMaini503 marked this pull request as ready for review June 10, 2025 17:58
@AMaini503 AMaini503 requested a review from a team as a code owner June 10, 2025 17:58
@RushabhBhansali RushabhBhansali changed the title Fix go detector UT Fix go detector Unit Tests Jun 10, 2025
@RushabhBhansali RushabhBhansali changed the title Fix go detector Unit Tests Fix Go detector Unit Tests Jun 10, 2025
@AMaini503 AMaini503 closed this Jun 10, 2025
@AMaini503 AMaini503 reopened this Jun 10, 2025
@AMaini503 AMaini503 merged commit a40ed24 into main Jun 10, 2025
42 of 46 checks passed
@AMaini503 AMaini503 deleted the user/aamaini/fixut-go branch June 10, 2025 18:23
@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.

2 participants