First off, thanks for taking the time to contribute! 🎉👍
This project and everyone participating in it is governed by the Zemit Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to contact@zemit.com.
Contributions to Zemit are greatly appreciated, whether they be code improvements, bug reports, feature requests, documentation updates, or any other enhancements.
Before creating bug reports, please check the issue list as you might find out that you don't need to create one. If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Provide as much detail and context as possible.
- Fill in the required template.
- Do not include issue numbers in the PR title.
- Include screenshots and animated GIFs in your pull request whenever possible.
- Follow the PHP Style Guide.
- Document new code based on the Documentation Styleguide.
- End all files with a newline.
- Avoid platform-dependent code.
Zemit can be developed locally. For instructions on how to do this, refer to Local Development.
- Use the present tense ("Add feature" not "Added feature").
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...").
- Limit the first line to 72 characters or less.
- Reference issues and pull requests liberally after the first line.
You can chat with the Zemit team and other community members on Discord, Slack, or GitHub Discussions.
Zemit Development Zemit Roadmap Thanks! Zemit Team