Skip to content

[feature] Add Preference Center key to selected content items #40192

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 19 commits into
base: master
Choose a base branch
from

Conversation

samuelFain
Copy link
Contributor

@samuelFain samuelFain commented Jun 5, 2025

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

relates: CIAC-13824

Description

A PR to add the compliantpolicies key to selected content items.

Caution

This PR should be merge only after the following PRs are merged (feature infrastructure):
#40043, demisto/demisto-sdk#4953, https://gitlab.xdr.pan.local/xdr/cortex-content/infra/-/merge_requests/978
Make sure to pull from master and verify green build before merging.

@samuelFain samuelFain closed this Jun 7, 2025
@samuelFain samuelFain force-pushed the sf-pref-center-update-content-items branch from ca0e10c to 51a03be Compare June 7, 2025 18:46
@samuelFain samuelFain reopened this Jun 7, 2025
Copy link
Contributor

@JasBeilin JasBeilin left a comment

Choose a reason for hiding this comment

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

Looks good, please revert some of the unintentional changes.

@samuelFain samuelFain requested a review from JasBeilin June 10, 2025 10:53
@samuelFain samuelFain added the ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines label Jun 10, 2025
@samuelFain samuelFain self-assigned this Jun 10, 2025
@samuelFain samuelFain marked this pull request as ready for review June 10, 2025 11:01
@content-bot
Copy link
Collaborator

Validate summary
The following errors were thrown as a part of this pr: RN111, RM108, PA114, ST111, BC104, BC102.
The following errors can be ignored: RM108.
The following errors cannot be ignored: RN111, PA114, ST111, BC104, BC102.
The following errors don't run as part of the nightly flow and therefore can be force merged: RN111, RM108, PA114, ST111, BC104, BC102.

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.

4 participants