Major integrations and fixes: - Added BACKBEAT SDK integration for P2P operation timing - Implemented beat-aware status tracking for distributed operations - Added Docker secrets support for secure license management - Resolved KACHING license validation via HTTPS/TLS - Updated docker-compose configuration for clean stack deployment - Disabled rollback policies to prevent deployment failures - Added license credential storage (CHORUS-DEV-MULTI-001) Technical improvements: - BACKBEAT P2P operation tracking with phase management - Enhanced configuration system with file-based secrets - Improved error handling for license validation - Clean separation of KACHING and CHORUS deployment stacks 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
17 lines
1013 B
Markdown
17 lines
1013 B
Markdown
# Contributing to Bleve
|
|
|
|
We look forward to your contributions, but ask that you first review these guidelines.
|
|
|
|
## Sign the CLA
|
|
|
|
As Bleve is a Couchbase project we require contributors accept the [Couchbase Contributor License Agreement](http://review.couchbase.org/static/individual_agreement.html). To sign this agreement log into the Couchbase [code review tool](http://review.couchbase.org/). The Bleve project does not use this code review tool but it is still used to track acceptance of the contributor license agreements.
|
|
|
|
## Submitting a Pull Request
|
|
|
|
All types of contributions are welcome, but please keep the following in mind:
|
|
|
|
- If you're planning a large change, you should really discuss it in a github issue or on the google group first. This helps avoid duplicate effort and spending time on something that may not be merged.
|
|
- Existing tests should continue to pass, new tests for the contribution are nice to have.
|
|
- All code should have gone through `go fmt`
|
|
- All code should pass `go vet`
|