Skip to content

empty change#43741

Open
mayyagoldman wants to merge 1 commit intomasterfrom
empty-sn-pr
Open

empty change#43741
mayyagoldman wants to merge 1 commit intomasterfrom
empty-sn-pr

Conversation

@mayyagoldman
Copy link
Copy Markdown
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

Description

Must have

  • Tests
  • Documentation

@mayyagoldman mayyagoldman added the ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines label Mar 30, 2026
@mayyagoldman mayyagoldman requested a review from dantavori as a code owner March 30, 2026 11:33
@content-bot
Copy link
Copy Markdown
Contributor

🤖 AI-Powered Code Review Available

You can leverage AI-powered code review to assist with this PR!

Available Commands:

  • @marketplace-ai-reviewer start review - Initiate a full AI code review
  • @marketplace-ai-reviewer re-review - Incremental review for new commits

@github-actions
Copy link
Copy Markdown

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/ServiceNow/Integrations/ServiceNowv2
   ServiceNowv2.py157028182%213, 225, 231, 479, 481, 485, 510, 551, 558–559, 597–598, 725–728, 738, 748–758, 769, 780–781, 853–854, 861, 867–873, 884–885, 898, 902, 915, 941, 943, 945–946, 948–949, 951–954, 956, 998, 1003, 1031–1036, 1039, 1042, 1153, 1294–1300, 1302, 1305–1306, 1308–1311, 1313, 1315–1316, 1318, 1320–1321, 1323–1324, 1326, 1349–1350, 1352, 1361–1362, 1393, 1432, 1435, 1442, 1470, 1475, 1563, 1618, 1666, 1712–1713, 1718, 1799, 1861, 1864, 1913, 1915–1917, 1919–1920, 1956, 1959–1961, 1975, 1980–1982, 2008, 2043–2044, 2052, 2103, 2147–2150, 2152, 2155, 2162, 2225–2230, 2232–2233, 2235–2237, 2239–2240, 2242–2244, 2246–2247, 2249, 2251, 2263, 2266, 2268, 2281–2286, 2288–2289, 2291–2293, 2295–2296, 2298–2300, 2302–2303, 2305, 2317–2318, 2321, 2323, 2341, 2344, 2372, 2375, 2409, 2412, 2416, 2444, 2484, 2510, 2540, 2638, 2650, 2661, 2664, 2668–2669, 2673, 2675–2676, 2748, 2754, 2765, 2813–2814, 2855–2858, 2880–2881, 2885–2886, 2921, 2925, 2931, 3023, 3026–3028, 3159–3163, 3165–3166, 3170–3171, 3226–3227, 3253, 3373, 3391, 3393, 3397–3398, 3571–3573, 3579, 3596, 3599, 3603, 3634, 3714, 3740–3741, 3746, 3762, 3783, 3804–3806, 3825–3827, 3869, 3877, 3933–3935, 3937, 3939, 3941, 3943, 3945, 3947, 3949, 3951, 3955, 3957, 3959, 3961–3962, 3967–3968, 3976
TOTAL157028182% 

Tests Skipped Failures Errors Time
177 0 💤 0 ❌ 0 🔥 27523485m 36s ⏱️

@content-bot
Copy link
Copy Markdown
Contributor

Validate summary
The following errors were thrown as a part of this pr: RN106, PA114.
The following errors cannot be ignored: RN106, 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, PA114.

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

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.

2 participants