Skip to content

Latest commit

 

History

History
40 lines (31 loc) · 1.25 KB

File metadata and controls

40 lines (31 loc) · 1.25 KB

YGIT Public Content Policy

Purpose

This repository is public. Every committed file must be safe for public distribution.

Allowed content

  • Product overview and verified capabilities
  • User onboarding and account-connection guidance
  • Repository analysis and deployment guides
  • CLI, SDK, and public API documentation
  • Public roadmap statements explicitly approved for publication
  • Sanitized screenshots and examples
  • Release notes and documentation updates

Prohibited content

  • Application source code from the private platform repository
  • Secrets, tokens, private keys, credentials, or production identifiers
  • Internal audit reports, implementation evidence, or operational runbooks
  • Exact internal commit identifiers and CI run identifiers
  • Private repository URLs
  • Vulnerability details that have not completed responsible disclosure
  • Features presented as available before they are verified and released

Publication workflow

Draft
→ Verify product behavior
→ Remove internal identifiers
→ Sanitize screenshots
→ Run public-content validation
→ Build the site
→ Review through pull request
→ Publish

Internal documents must be rewritten for the intended public audience. They must never be copied verbatim by default.