Druks is alpha software. Discussion before a large change is useful because the public extension surface and deployment model are still moving.
- Search existing issues and open one for behavior changes or substantial work.
- Read the development guide and the relevant concept, operator, or extension-author guide.
- Keep platform behavior separate from application-specific extension policy.
- Add focused tests for behavior changes and update the canonical public guide when a contract changes.
Run the repository checks that cover your change. The complete commands are in the development guide. A pull request should say exactly what was run and explain any check that could not run.
- Keep each pull request focused and explain the user-visible outcome.
- Call out migrations, workflow replay compatibility, external side effects, security boundaries, and deployment changes explicitly.
- Do not commit credentials, local configuration, exports, research, generated
build output, or files under
tmp/. - By contributing, you agree that your contribution is licensed under the repository's MIT License.
Security reports do not belong in public issues. Follow SECURITY.md.