kabu 0.6.0

CLI tool to enhance git worktree and jj workspace with automated setup
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83

# Contributing to kabu

Thank you for considering contributing to kabu! We welcome all contributions, including:

- Bug reports
- Feature requests
- Documentation improvements
- Code contributions

## Requirements

- Rust 1.85 or higher
- cargo

## Development

### Setup

1. Fork the repository
2. Clone your fork:
   ```bash
   git clone https://github.com/YOUR_USERNAME/kabu.git
   cd kabu
   ```
3. Build the project:
   ```bash
   cargo build
   ```

### Development Commands

```bash
# Run tests
cargo test

# Check formatting
cargo fmt --all --check

# Format code
cargo fmt

# Run clippy lints
cargo clippy

# Fail on clippy warnings (CI standard)
cargo clippy -- -D warnings
```

## Commit Messages

We recommend using [Conventional Commits](https://www.conventionalcommits.org/) format for commit messages:

- `feat: Add new feature` - New features
- `fix: Fix bug description` - Bug fixes
- `docs: Update documentation` - Documentation changes
- `perf: Improve performance` - Performance improvements
- `refactor: Refactor code` - Code refactoring
- `chore: Update dependencies` - Chores and maintenance tasks

### CHANGELOG

The CHANGELOG is automatically generated using [git-cliff](https://git-cliff.org/). Only commits matching the above types will appear in the CHANGELOG. The following commits are excluded:

- `chore(release): ...` - Release preparation commits
- `chore.*CHANGELOG` - CHANGELOG update commits

**Note:** Conventional Commits format is recommended but not required. Non-conventional commits simply won't appear in the auto-generated CHANGELOG.

## Pull Requests

1. **Discuss first**: For large changes, please open an issue first to discuss the proposed changes.
2. **Make your changes**: Ensure all tests pass and code is properly formatted.
3. **Submit PR**: Open a pull request with a clear description of your changes.
4. **Merge strategy**: We use regular merge (not squash merge) to preserve commit history.

## License

By contributing to kabu, you agree that your contributions will be licensed under either:

- MIT License
- Apache License 2.0

at the user's option, matching the project's dual licensing.