Skip to content

add provider to core packs#42529

Merged
kobymeir merged 9 commits intomasterfrom
add-provider-core-packs
Jan 6, 2026
Merged

add provider to core packs#42529
kobymeir merged 9 commits intomasterfrom
add-provider-core-packs

Conversation

@Shir2611
Copy link
Copy Markdown
Contributor

@Shir2611 Shir2611 commented Jan 4, 2026

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

@Shir2611 Shir2611 added docs-approved ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines labels Jan 4, 2026
Copy link
Copy Markdown
Contributor

@israelpoli israelpoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great 💪
see below comments

Comment thread Packs/Core/Integrations/CoreIOCs/CoreIOCs.yml
Comment thread Packs/HelloWorld/Integrations/HelloWorld/HelloWorld.yml Outdated
@israelpoli israelpoli self-requested a review January 4, 2026 15:02
@Shir2611 Shir2611 requested a review from MosheEichler as a code owner January 4, 2026 15:43
@adi88d adi88d removed their request for review January 5, 2026 08:15
@israelpoli
Copy link
Copy Markdown
Contributor

A force is required due to validations failing as a result of the version not being bumped.
This is not actually required, since there is supposed to be a specific upload process for the core packs

@israelpoli israelpoli added the ForceMerge Forcing the merge of the PR despite the build status label Jan 5, 2026
@Shir2611
Copy link
Copy Markdown
Contributor Author

Shir2611 commented Jan 6, 2026

this is the "add provider" task
we added provider to all core packs
we need force merge as some validations are failing

@content-bot
Copy link
Copy Markdown
Contributor

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

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

@kobymeir kobymeir merged commit 00b016e into master Jan 6, 2026
18 of 20 checks passed
@kobymeir kobymeir deleted the add-provider-core-packs branch January 6, 2026 09:16
barryyosi-panw pushed a commit that referenced this pull request Jan 6, 2026
* add provider to core packs

* add provider to core packs

* add provider to core packs

* add provider to core packs

* add provider to core packs

* Empty commit

* add provider to core packs

* fix ruff format

---------

Co-authored-by: ipolishuk <ipolishuk@paloaltonetworks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-approved ForceMerge Forcing the merge of the PR despite the build status 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.

4 participants