Contributing on Divekit

Development Setup

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally stays short. The detailed development-setup workflow changes together with the CLI repository and is maintained there to avoid duplication.

Stable Summary

Clone divekit-cli
Use Go 1.24+
Build with make build
Run checks with make check
Use the CLI repo’s Local GitLab guide when local GitLab is required

Source of Truth

For the current step-by-step setup, use:

Error Handling

Mon, 01 Jan 0001 00:00:00 +0000

Divekit uses a centralized categorized error model built around internal/error (apperror), command middleware, and internal/shell/logging.

This page is now only a summary. The implementation-coupled source of truth lives in the CLI repository under docs/architecture/error-handling.md.

Stable Summary

commands should return typed errors, not format terminal output themselves
user messages and technical details should stay separate
exit codes are determined centrally
logging should go through the shared logging package
fallback behavior should be explicit and observable

For package paths, current examples, and maintainer-level guidance, use the CLI repository document.

Contributing Guidelines

Mon, 01 Jan 0001 00:00:00 +0000

This page keeps only the stable contribution expectations. The current contributor workflow is maintained in the CLI repository under CONTRIBUTING.md.

Stable Expectations

Make code changes in the CLI repository.
Update tests and documentation when behavior changes.
Run the relevant checks before opening a merge request.
Keep user-facing text in English.
Prefer consistency with existing command, handler, and error-handling patterns.

Source of Truth

Use the CLI repository for current details about: