Skip to content

Latest commit

 

History

History
69 lines (42 loc) · 2 KB

File metadata and controls

69 lines (42 loc) · 2 KB

Summary

Closes #


Type of change

  • feat — new page or substantial content addition
  • fix — corrects a factual error, broken link, or bad code example
  • docs — changes to meta-docs (CONTRIBUTING.md, README.md, templates)
  • chore — tooling, CI, config, or dependency update
  • refactor — content restructuring without meaning changes
  • style — formatting only

Conventional commit checklist

  • My PR title starts with a conventional-commit type such as feat, fix, docs, chore, refactor, or style
  • The title is short, lowercase, and follows the format type(scope): summary
  • My commit messages follow the same convention where applicable

Branch checklist

Common mistakes that cause PRs to be redirected. Please verify before opening.

  • I branched from develop, not main
  • This PR targets develop, not main

Content checklist

  • All new or modified pages have at least one code example (if applicable)
  • Code examples use TypeScript, @wraith-protocol/sdk, and the Chain enum — not raw strings
  • No marketing copy — descriptions explain what, not how great

Snippet checklist

  • I ran pnpm run check:snippets locally and it passes
  • All new TypeScript/JavaScript fences compile without errors
  • I used no-check only for intentionally illustrative pseudocode that cannot be made runnable

Screenshots or previews


Additional notes