Skip to content

Latest commit

 

History

History
21 lines (14 loc) · 1.08 KB

File metadata and controls

21 lines (14 loc) · 1.08 KB

Contributing

Thank you for improving the Nexscope Creative API examples.

Before opening a pull request

  1. Keep all public repository content in English.
  2. Never include API keys, tokens, customer data, private URLs, generated customer assets, or internal infrastructure details.
  3. Use the public API endpoint format documented in the root README.
  4. Add or update the sample payload, catalog entry, and public documentation link together.
  5. Preserve the repository-wide co-from=githubcreative channel code on Nexscope website links.
  6. Run python3 scripts/validate_repository.py.
  7. Do not make live API calls in tests or continuous integration.

Pull request scope

Keep each pull request focused. Explain which API or example changed, why it changed, and which checks were run. Example values must be synthetic, public, or taken from published Nexscope documentation.

Issues

Use GitHub issues for reproducible example-code problems and documentation gaps. Do not post API keys, account details, full paid responses, customer assets, or security vulnerabilities in a public issue.