Contributing

Start with the first contribution walkthrough.

Browse good first issues for a bounded change, or help wanted for broader projects. Documentation fixes, reproductions, and manual verification are welcome alongside code contributions. Comment on the issue before starting and ask questions there; no chat account is required.

Follow the contribution guide for repository boundaries, change scope, and verification expectations.

bun install --frozen-lockfile
bun run check
bun run test
bun run build

Keep a pull request focused. Add tests for behavior changes and update the docs when a public contract changes.

Use a branch such as fix/dsui-123-wrap-long-values, with the synced Linear ID listed in the GitHub issue. Ask a maintainer if the ID is missing. PRs from forks follow the same naming rule. Include both Fixes #<github-issue-number> and Fixes DSUI-<linear-id> in the PR description.

For documentation-only work, check links and examples and build the changed surface. See the contribution guide for focused commands and the repository map.

For an adapter, start from the Adapter SDK. Validate the connection, keep credentials server-side, and state the coverage and limitations explicitly.

The complete example adapter shows package setup, tests, local loading, resources, actions, pages, and optional browser components. Use it as the practical starting point for a new adapter.