Skip to content

Conversation

@umishkin
Copy link
Contributor

@umishkin umishkin commented Nov 3, 2025

…ng enriched indicators

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

@umishkin umishkin requested a review from OmriItzhak November 3, 2025 21:53
@umishkin umishkin added ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines docs-approved labels Nov 3, 2025
@umishkin umishkin removed the request for review from JudahSchwartz November 3, 2025 22:01
@content-bot
Copy link
Collaborator

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

docs-approved 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