Skip to content

Latest commit

 

History

History
74 lines (48 loc) · 1.98 KB

File metadata and controls

74 lines (48 loc) · 1.98 KB

Contributing to kubert

Thank you for your interest in contributing to kubert! This document provides guidelines and instructions for setting up your development environment and contributing to the project.

Development Prerequisites

  • Go (check go.mod for minimum version)
  • golangci-lint (check golangci-lint for installation instructions)
  • Make (optional, but recommended)

Getting Started

  1. Clone the repository
git clone https://github.com/idebeijer/kubert.git
cd kubert
  1. Run from Source

To run the project locally for example with a custom configuration:

go run main.go --config config.yaml
  1. Build and Test

You can use make to run common tasks:

make lint
make test
make build
# Build a snapshot release locally with goreleaser at ./dist (does not publish)
make goreleaser-release-snapshot
  1. Update Documentation

If you modify CLI commands or add examples, please regenerate the documentation in ./docs:

make docs

Commit Messages

We use Conventional Commits for our commit messages. Since we squash commits upon merging, the individual commits in your Pull Request do not necessarily need to follow this convention, but the PR title should.

The changelog is automatically generated based on these conventional commits, sorting them by type (e.g., feat goes under Features, fix under Bug fixes).

Format

Follow the conventional commit format:

  • feat: add new feature
  • fix: resolve bug
  • docs: update documentation
  • test: add or update tests
  • refactor: code refactoring
  • chore: maintenance tasks

Breaking Changes

Indicate breaking changes by appending a ! after the type/scope:

  • feat!: change something
  • feat(api)!: remove deprecated endpoint

License

By contributing, you agree that your contributions will be licensed under the MIT License.