Skip to content

Conversation

shmuel44
Copy link
Contributor

@shmuel44 shmuel44 commented Sep 8, 2025

No description provided.

Copy link

github-actions bot commented Sep 8, 2025

Your contributed PolySwarm pack has been modified on files:

Packs/PolySwarm/pack_metadata.json
Packs/PolySwarm/ReleaseNotes/2_0_10.md
Packs/PolySwarm/Integrations/PolySwarmV2/PolySwarmV2.yml
Please review the changes here

@content-bot
Copy link
Collaborator

⚠️ The PR is missing the ready-for-pipeline-running label. Please add the label when the PR is ready in order to proceed.

Copy link

github-actions bot commented Sep 8, 2025

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/PolySwarm/Integrations/PolySwarmV2
   PolySwarmV2.py1976368%18, 20, 55, 57–63, 65, 70, 75–76, 89, 92, 133–134, 148–149, 156–157, 177–178, 193–194, 215–216, 224, 234–235, 247–249, 285–287, 289–290, 292–294, 296–314, 316–317
TOTAL1976368% 

Tests Skipped Failures Errors Time
8 0 💤 0 ❌ 0 🔥 1m 49s ⏱️

@content-bot
Copy link
Collaborator

Validate summary
The following errors were thrown as a part of this pr: .
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.

Verdict: PR can be force merged from validate perspective? ✅

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