Skip to content

Latest commit

 

History

History
32 lines (23 loc) · 1.09 KB

File metadata and controls

32 lines (23 loc) · 1.09 KB

GitHub Publishing Checklist

Use this checklist before making a Kaya Flow-derived repository public.

Repository Settings

  • Visibility is intentional.
  • The repository is marked as a template if you want others to click "Use this template".
  • Secret scanning and push protection are enabled when available.
  • Topics describe the project clearly.
  • The description explains the draft-only positioning.

Before The First Public Push

  • No real brand names, customer names, investor names, or partner names.
  • No private drafts, research, topics, or logs.
  • No .env, .mcp.json, API keys, account IDs, or publisher config.
  • No live publishing workflows.
  • Git history is clean or intentionally public from the first commit.

Suggested Topics

ai content-workflow content-strategy prompt-engineering brand-voice agent-workflow docs-as-code draft-only

Release Checklist

  1. Update CHANGELOG.md.
  2. Tag the release with semantic versioning, such as v0.1.0.
  3. Create a GitHub release with a short summary and safety notes.
  4. Confirm the README quickstart still works from a fresh clone.