Thanks for contributing to dwarvenpick.
- Create a focused branch for your change.
- Keep diffs small and scoped to one concern.
- Run relevant local checks before opening a PR.
Backend:
./gradlew clean ktlintCheck testFrontend:
cd frontend
npm ci
npm run lint
npm run format:check
npm run test
npm run build- Use Conventional Commits for commit messages (for example
feat: add version endpoint). - Use short, conventional-style branch names (for example
feat/add-version-endpoint).
- Describe the intent and user impact clearly.
- Reference related issue(s) or discussion(s) when applicable.
- Include test evidence in the PR description.