Issues and support
What the public repository contains
Section titled “What the public repository contains”The graphics-packages repository provides public SDK and CLI downloads and a scoped issue tracker. The implementation source remains in a private repository.
Releases contain versioned SDK and CLI archives, release notes, and checksums. You do not need a GitHub or npm account to download them. A GitHub account is required to open an issue. LIGR API authentication is separate.
Choose the right channel
Section titled “Choose the right channel”| Topic | Where to go |
|---|---|
| Code graphics authoring, runtime, protocol, or theme publishing bugs | GitHub Issues |
| SDK or CLI installation, commands, validation, or package bugs | GitHub Issues |
| Code graphics, SDK, or CLI questions, concerns, and feature requests | GitHub Issues |
| Incorrect code graphics documentation or examples | GitHub Issues |
| Broken app or documentation pages, login, account access, billing, or general platform problems | LIGR support or in-app support |
GitHub Issues covers the code graphics platform and its developer tools. This includes plain HTML, CSS, JavaScript, and any browser rendering library.
Open a useful issue
Section titled “Open a useful issue”- Search existing issues for the same problem or request.
- Open a new issue and select the matching form.
- For a bug, include package versions, browser or Node version, reproduction steps, and expected and actual results.
- For a feature request, explain the code graphics use case and the behavior you need.
- For a documentation correction, link the relevant example or instruction and describe the error.
Issues are public. Remove API keys, credentials, private URLs, and customer data from examples and logs before posting. Use LIGR support for reports that require private account information.
Automated issue checks
Section titled “Automated issue checks”The issue bot checks the required form fields and declared topic when you open, edit, or reopen an issue. It can close incomplete reports or reports explicitly marked as general app or account problems. Its reply lists each failed requirement and explains how to correct the report or contact support.
These checks help developers spend time investigating and fixing actionable code graphics problems. They are not a penalty for reporting a problem. We value your reports and apologize for the problems you encounter.
If the bot closes your code graphics issue, edit it to address the listed requirements. The bot rechecks the report and reopens it when the requirements are met. Uncertain scope stays open for review, and maintainers can override the automated checks.