Remove Response JSON format samples from Secure report docs
Problem to solve
We currently include samples of each devopssecure report within our docs pages. These are prone to being out of date and containing inaccuracies and now that we have a dedicated security report schema repository, we should remove the samples to ensure our documentation stays up to date
Intended users
User experience goal
More accurate documentation for customers, lower maintenance burden for maintainers.
Proposal
Remove Report Format JSON
from Secure documentation pages:
- https://docs.gitlab.com/ee/user/application_security/sast/index.html#reports-json-format
- https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#reports-json-format
- https://docs.gitlab.com/ee/user/application_security/container_scanning/#reports-json-format
Further details
Permissions and Security
N/A
Documentation
More betterer
Availability & Testing
N/A
What does success look like, and how can we measure that?
Clearer docs
What is the type of buyer?
GitLab Ultimate mostly
Is this a cross-stage feature?
devopssecure groupcomposition analysis groupstatic analysis
Links / references
Edited by Lucas Charles