PR Gates - new product flow [DOCS-10684] #30713
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Smol change for testing, open PR
joepeeples
added
WORK IN PROGRESS
ℹ️ Documentation Team ReviewNo documentation team review is required for this pull request. |
joepeeples
changed the title
Preview links (active after the
|
1 task
no Explorer view currently
Search not currently available, and no longer enough content to justify having a separate Manage page. Also adds redirect alias for the removed page.
joepeeples
added a commit
that referenced
this pull request
Jul 31, 2025
The "Executions" page in the app no longer exists, so links to it will 404. For now I'm just changing to the main PR Gates app page to avoid breaks, and we'll remove the full Explorer content & links in #30713
…es-new-product-flow
forgot to save
…es-new-product-flow
…es-new-product-flow
…es-new-product-flow
Audit Trail does not seem supported yet for PR Gates
joepeeples
added
editorial review
|
Opened DOCS-11772 for editorial review. |
…es-new-product-flow
drichards-87
approved these changes
Aug 12, 2025
content/en/pr_gates/_index.md
Outdated
| | [**Static Code Analysis**][11] | <li> Code vulnerability violations <li> Code quality violations | | ||
| | [**Software Composition Analysis**][12] | <li> Library vulnerability violations <li> Detected license violations | | ||
| | [**Code Coverage**][15] | <li> Total code coverage threshold <li> Patch code coverage threshold | | ||
| | [**Infrastructure as Code Scanning**][16] | <li> IaC vulnerability severity | |
There was a problem hiding this comment.
Just noting that we recently changed the name to Infrastructure as Code Security. But it looks like the UI still refers to it as Infrastructure as Code Scanning. Could we pass this feedback along to the PR Gates PM?
markazerdd
reviewed
Aug 15, 2025
Co-authored-by: Mark Azer <[email protected]>
Co-authored-by: DeForest Richards <[email protected]>
Co-authored-by: Mark Azer <[email protected]>
…es-new-product-flow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Revises documentation for new PR Gates product.
Important
This PR builds on and targets the product renaming branch in #29089. When we're ready to merge, we need to merge the renaming PR first, then rebase this PR to
main. This shouldn't affect any content being reviewed in the current PR.Tip
For reviewers: Because of extensive revisions to multiple sections, the diff tab in GitHub looks pretty choppy and isn't great for reviewing. It's probably easier to review the preview as a whole, focusing on the main landing page and Setup page.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass 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.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes