Druks is alpha software. Discuss a large change before you start it. The public app surface and deployment model can change.
- Search the existing issues. Open an issue for a behavior change or substantial work.
- Read the development guide.
- Read the applicable concept, operator, or app-author guide.
- Keep platform behavior separate from app-specific policy.
- Add focused tests for a behavior change.
- If a contract changes, update the canonical public guide.
Run the repository checks that cover your change. The complete commands are in the development guide. In the pull request, list each command that you ran. Explain each command that you did not run.
- Keep each pull request focused. Explain the user-visible result.
- Identify migrations, workflow replay compatibility, external side effects, security boundaries, and deployment changes.
- Do not commit credentials, local configuration, exports, research, generated
build output, or files under
tmp/. - Your contribution uses the repository's MIT License.
Security reports do not belong in public issues. Follow SECURITY.md.