Writing and maintaining GitHub issues for the tldraw repository. Use when creating new issues, editing issue titles/bodies, triaging issues, or cleaning up issue metadata (types, labels).
Standards for issues in tldraw/tldraw.
Bug:, Feature:, [Bug], etc.Arrow bindings break with rotated shapesAdd padding option to zoomToFit methodPinch zoom resets selection on SafariBug: arrow bug (prefix, vague)[Feature] Add new feature (prefix, vague)Not working (vague)Bug: X → XAdd Padding Option → Add padding optionAdding feature X → Add feature XProblem → [Describe the actual problem]Set via the GitHub GraphQL API after creating the issue (the --type flag is not reliably supported):
| Type | Use for |
|---|---|
Bug | Something isn't working as expected |
Feature | New capability or improvement |
Example | Request for a new SDK example |
Task | Internal task or chore |
Use sparingly (1-2 per issue) for metadata, not categorization.
| Label | Use for |
|---|---|
good first issue | Well-scoped issues for newcomers |
More Info Needed | Requires additional information |
sdk | Affects the tldraw SDK |
dotcom | Related to tldraw.com |
a11y | Accessibility |
performance | Performance improvement |
api | API change |
keep, stale, update-snapshots, publish-packages, major, minor, skip-release, deploy triggers
More Info Needed label and comment if details missinggood first issue if appropriatekeep label if should remain open