-
Notifications
You must be signed in to change notification settings - Fork 1.2k
DOCS-10634: Remove preview banners from Automation Pipelines docs #28788
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I inadvertently flagged API Security Finding but realize it's singular in the app!
- Application Code Vulnerability | ||
- Application Library Vulnerability | ||
- Container Image Vulnerability | ||
- API Security Finding |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- API Security Finding | |
- API Security Findings |
Not sure if this should be plural ?
- **Application Code Vulnerability** | ||
- **Application Library Vulnerability** | ||
- **Container Image Vulnerability** | ||
- **API Security Finding** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- **API Security Finding** | |
- **API Security Findings** |
Actually disregard! I see this is singular in the app :)
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
…8788) * Remove preview banners * Additional edits
…8788) * Remove preview banners * Additional edits
What does this PR do? What is the motivation?
DOCS-10634. Removes preview banners from Automation Pipelines docs. Also includes misc. updates to align with new terminology (findings vs. vulnerabilities).
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes