We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
- π Reporting a bug
- π‘ Discussing the current state of the code
- π Submitting a fix
- β¨ Proposing new features
- π Becoming a maintainer
- π Open Development
- π Code of Conduct
- π Bug Reports
- π§ Prerequisites
- π Pull Request Process
- β Miscellaneous
This project is open-source under the MIT license. All development happens here on GitHub. We welcome contributions from the community!
This project and everyone participating in it are governed by our Code of Conduct. By participating, you are expected to uphold this code. Please read the full text to understand what behaviors are expected and which are not tolerated.
We use GitHub Issues to track public bugs. Before creating a new issue, please check if your problem has already been reported.
Before you start contributing, ensure you have:
Note: This project uses Yarn as the package manager. Please use Yarn for all package installations.
Our team will review your pull request and either merge it, request changes, or close it.
-
Setup Your Environment
- Fork the repository and create your branch from
main - Run
yarn installin the repository root - Run
yarn preparein the repository root to installpre-commithooks - For bug fixes or new features, add tests and link the corresponding issue
- Ensure all tests pass:
yarn test:server - Verify code quality:
yarn lint
- Fork the repository and create your branch from
-
Documentation
- Update the README.md with any interface changes
- Include new environment variables, ports, file locations, or container parameters
-
Commit Sign-off
- Sign-off all your commits using the following format:
This is my commit message Signed-off-by: Your Name <your.email@example.com>
- Or use Git's
-sflag:
git commit -s -m 'Your commit message' -
Review Process
- A maintainer will review your PR
- They may suggest modifications
- Once approved, they will merge and close your request
Before submitting an issue, please ensure:
-
Issue Validation
- You're experiencing a concrete technical issue with the plugin
- You've searched for existing issues and found none open
- Your issue title is clear, concise, and professional
-
Reproduction Steps
- You can provide clear steps to reproduce the issue
- You've tried the following troubleshooting steps:
- Verified the correct application is running
- Followed the issue template
- Formatted your issue properly using GitHub Markdown
- Restarted the Strapi server (CTRL+C and restart)
- Cleaned your
node_modules:rm -rf node_modules && npm cache clear && npm install
- Verified no dependencies are linked
- Confirmed no inline changes in
node_modules - Checked for global dependency loops