9bdcbe0447
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>
27 lines
956 B
Markdown
27 lines
956 B
Markdown
# How to contribute
|
|
|
|
We definitely welcome patches and contribution to this project!
|
|
|
|
### Tips
|
|
|
|
Commits must be formatted according to the [Conventional Commits Specification](https://www.conventionalcommits.org).
|
|
|
|
Always try to include a test case! If it is not possible or not necessary,
|
|
please explain why in the pull request description.
|
|
|
|
### Releasing
|
|
|
|
Commits that would precipitate a SemVer change, as described in the Conventional
|
|
Commits Specification, will trigger [`release-please`](https://github.com/google-github-actions/release-please-action)
|
|
to create a release candidate pull request. Once submitted, `release-please`
|
|
will create a release.
|
|
|
|
For tips on how to work with `release-please`, see its documentation.
|
|
|
|
### Legal requirements
|
|
|
|
In order to protect both you and ourselves, you will need to sign the
|
|
[Contributor License Agreement](https://cla.developers.google.com/clas).
|
|
|
|
You may have already signed it for other Google projects.
|