Skip to content
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

Run Modeling/Parsing Rules YMLs Alignment second and third chunks #38362

Merged
merged 8 commits into from
Jan 28, 2025

Conversation

AviShakuri
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

@AviShakuri AviShakuri requested a review from eepstain January 28, 2025 09:16
@eepstain eepstain added docs-approved ForceMerge Forcing the merge of the PR despite the build status bypass.url Whether to create build bucket, add this label for marketplace.bootstrap.bypass.url labels Jan 28, 2025
@eepstain
Copy link
Contributor

This is a part of the YML config alignment as a part of the validations revision for fromversion and toversion checks. CIAC-12402.

We need a Force Merge for this, making sure all the IDs and Names in the YML configs are aligned.

@tkatzir tkatzir merged commit bc234cf into master Jan 28, 2025
24 of 26 checks passed
@tkatzir tkatzir deleted the CRTX-151321-second-third-chunks branch January 28, 2025 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bypass.url Whether to create build bucket, add this label for marketplace.bootstrap.bypass.url docs-approved ForceMerge Forcing the merge of the PR despite the build status
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants