Code Coverage GA #31848
Open
Code Coverage GA #31848
+17
−15
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
rtrieu
approved these changes
Sep 25, 2025
There was a problem hiding this comment.
We would like to make Code Coverage GA in 2 stages:
- Go from private preview to public preview: make the product available to everyone without the need to request access through the signup form.
- Go from public preview to GA: start billing the customers for using the product.
The first phase will happen in the next 1-2 weeks, while the second one will require more time (not sure how much more, could be until the end of the year).
I wonder if for now it makes sense to remove the mentions of the signup form but leave the note saying that the product is in preview. I'm trying to think of how to make the billing implications clearer to the customers
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 banners to remove Preview information, but still distinguish the Code Coverage product from the legacy code coverage feature in Test Optimization.
Merge instructions
Merge readiness:
Note
WAIT until product is fully GA before merging, but go ahead and review/approve to have the PR ready to merge when needed.
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