Skip to content

Conversation

@hyaffe839
Copy link
Contributor

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

  • In Progress
  • Ready
  • In Hold - (Reason for hold)

Related Issues

fixes: link to the issue

Description

A few sentences describing the overall goals of the pull request's commits.

Must have

  • Tests
  • Documentation

@github-actions
Copy link

github-actions bot commented Jul 22, 2025

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/CortexXDR/Integrations/CortexXDRIR
   CortexXDRIR.py6919186%56, 64, 68–70, 141–142, 225–229, 231, 233, 236, 241, 268–272, 274, 281–284, 304, 307, 310, 316, 319, 352, 356–359, 361, 369, 371–374, 377–381, 383, 471–474, 476, 530, 568, 584–585, 604, 614, 678, 681, 714, 721, 723, 787–788, 790, 841, 922, 1043–1044, 1047, 1097–1098, 1119, 1160–1163, 1217, 1234–1236, 1241, 1246, 1274–1277, 1309, 1325
Packs/CortexXpanse/Integrations/CortexXpanse
   CortexXpanse.py6099983%333–338, 340–341, 343–345, 347–348, 431, 433, 447, 451, 455, 457–458, 469–470, 479, 483–484, 491, 525, 529, 531, 565, 625, 759, 802, 804, 806, 844, 847, 883, 886, 922, 925, 961, 964, 1016, 1018, 1033, 1037, 1042, 1051, 1092, 1141, 1147, 1149, 1175, 1221, 1224, 1226, 1231, 1233, 1235–1236, 1238, 1277, 1280, 1285, 1341, 1350, 1354, 1363, 1426, 1429, 1448, 1511–1512, 1514–1519, 1521–1523, 1533–1535, 1537–1538, 1583–1586, 1612, 1614, 1624, 1626, 1630, 1632–1633
TOTAL130019085% 

Tests Skipped Failures Errors Time
41 0 💤 0 ❌ 0 🔥 3.493s ⏱️

@hyaffe839 hyaffe839 added the ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines label Jul 24, 2025
@content-bot
Copy link
Collaborator

Validate summary
The following errors were thrown as a part of this pr: RN106, DO106, PA114.
The following errors cannot be ignored: RN106, DO106, PA114.
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.
The following errors don't run as part of the nightly flow and therefore can be force merged: RN106, DO106, PA114.

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

@hyaffe839 hyaffe839 closed this Aug 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants