Update JetBrians code security page to mention Secret Scanning#36694
Conversation
Preview links (active after the
|
buraizu
left a comment
There was a problem hiding this comment.
Thanks for the PR, left a couple of minor suggestions. Additionally, flagging that there seems to be some inconsistency now with other sections of the page that still use the previous terminology. For example:
- Line 52: Show Datadog Static Analyzer Config action label.
- Line 65: "The Datadog Static Analyzer can be activated and deactivated in the IDE settings under Editor → Inspections."
- Line 67 alt text: "Settings to activate and deactivate Static Analysis."
Could you please confirm if these need to be updated as well?
Additionally, could you please restore the old image and upload the new image with a new filename (and update the image references in the page as well)? This prevents caching issues in the translated docs, as updates to the English language docs take some time to propagate to the translated docs. Let me know if you have any questions, and I can point you toward some internal resources with more information.
Co-authored-by: Bryce Eadie <bryce.eadie@datadoghq.com>
…ext and few other areas
That is still called Static Analyzer Config (
Renamed and updated screen shot
Changed to Code Security
Done |
What does this PR do? What is the motivation?
Updates the JetBrains docs to mention Secret Scanning and the renamed inspection from
Datadog Static Analysis->Datadog Code SecurityMerge 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.
AI assistance
Additional notes