Skip to content

docs: add query_history redaction checklist #15

Description

@sionsmith

Task

Document how users should redact QUERY_HISTORY exports before attaching examples to issues or sharing benchmark data.

Likely files

  • SECURITY.md
  • docs troubleshooting or replay simulator page

Acceptance criteria

  • Checklist covers query text, account identifiers, usernames, roles, warehouses, database/schema/table names, and timestamps.
  • The checklist says security reports should stay private.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationgood-first-issueGood for newcomershelp-wantedExtra attention is needed

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions