CONTRIBUTION.md, issue templates, pull-request template, root license, and ee/LICENSE when enterprise code is involved.
1
Choose or open an issue
Confirm the problem, expected behavior, affected application, and whether the change belongs in open-source or enterprise code.
2
Fork and branch
Create a short-lived branch from the current target branch. Keep unrelated refactors out of the change.
3
Develop locally
Follow local development and match the existing domain/module patterns.
4
Verify proportionally
Run focused tests while iterating, then lint, type-check, build, and integration checks relevant to the changed packages.
5
Open a pull request
Explain the user impact, implementation, testing, screenshots/API examples, configuration changes, and rollout/rollback concerns.
Good first contribution areas
Documentation
Correct a source-aligned guide, expand OpenAPI annotations, or add troubleshooting evidence.
Tests
Add regression coverage for gateway modules, middleware, queue behavior, or browser widget protocol.
Adapters
Improve a provider implementation behind an existing interface with failure and security tests.
Accessibility
Improve keyboard, screen-reader, contrast, and responsive behavior in console or widget.
Generated artifacts, secrets, local
.env files, and dependency directories do not belong in pull requests.