Thank you for your interest in contributing to Phala Cloud SDKs! This guide outlines the requirements for contributing to this project.
This project follows Conventional Commits specification. All commits must adhere to this format:
<type>(<scope>): <subject>
feat: A new featurefix: A bug fixdocs: Documentation only changesstyle: Changes that do not affect the meaning of the code (formatting, etc.)refactor: Code change that neither fixes a bug nor adds a featuretest: Adding missing tests or correcting existing testschore: Changes to the build process or auxiliary toolsperf: Performance improvementsci: Changes to CI configuration files and scriptsbuild: Changes that affect the build system or external dependenciesrevert: Reverts a previous commit
feat: add user authentication to CLI
fix: resolve memory leak in API client
docs: update README with installation steps
chore(deps): bump axios to 1.7.9
refactor(cli): simplify config loading logic
All pull requests will be automatically checked for commit message compliance. If your commits do not follow the convention, the PR check will fail with guidance on the correct format.
Note: Commit messages are used to automatically generate changelogs, so following this convention is important for project maintenance.
To submit a new template, please follow these steps:
- Modify
templates/config.jsonand add your template entry following the schema format - Ensure your repository directory contains the following files:
README.md: Detailed documentation and usage instructionsdocker-compose.yml: Deployment configuration
- Update the project's
README.mdto include your template in the list of available templates - (Optional) Add an icon in the
templates/iconsdirectory: - (Optional) Add a "Deploy to Phala Cloud" button to your template's
README.md:Replace[](https://cloud.phala.com/templates/{template_id})
{template_id}with your actual template ID
Thank you for your contribution!