Attachments and Supporting Docs

Attachments are supporting files you link to a change list (repo or workspace) or a stash. They can be anything that helps others understand, validate, or reuse the work: documents, logs, telemetry, binaries, profiling output, screenshots, and more.

Why Attachments Matter

Attachments make collaboration easier because they keep context with the change itself. Teammates can review evidence, reproduce results, and audit decisions without chasing files across chat, email, or build systems. They are also the best place to store information an LLM can use for high‑quality summaries, reviews, and risk analysis.

Attachment Scopes

Repo changelist attachments

Durable attachments tied to submitted change lists. Use these for long‑term context that should live with history (final review notes, approvals, release artifacts).

Workspace changelist attachments

Attachments tied to pending change lists. Use these for work‑in‑progress context (draft notes, local test output, interim builds).

Stash attachments

Attachments tied to a stash (local or remote). Use these when you want to capture WIP context alongside a stashed snapshot. Remote stash attachments are shareable depending on stash access rules.

Common Uses

• Peer review notes, design notes, and decision records.
• Test reports, profiling output, telemetry bundles.
• Build outputs and pre‑compiled binaries.
• AI‑generated summaries, reviews, and risk notes (optional and advisory).

Cautions and Good Practices

• Attachments are supplemental; keep the change list description clear and complete.
• Avoid secrets or sensitive data in attachments unless your access rules explicitly allow it.
• Large artifacts are fine, but attach them intentionally so reviewers know what to expect.