Thank you for your interest in contributing to Aster, we welcome contributions of all kinds! Please read below for instructions to follow.
If you find a bug in one of our services, open an issue on the relevant repository. Please make sure to include as much detail as possible:
- What you expected to happen
- What actually happened to cause it
- Steps to reproduce the bug
- Your operating system, browser, app version, and any other relevant details or notes
For any security vulnerabilities, make sure not to open a public issue. Please read our Security Policy for instructions on how to properly report a vulnerability.
Open an issue with the label suggestion. Make sure you describe the problem that you are trying to solve and not just the solution. It helps us understand the exact use case of the suggestion
- Fork the relevant repository
- Create a new branch:
git checkout -b your-feature-name - Make any changes that you would like
- Do full end-to-end testing of your changes thoroughly
- Commit your changes with a clear message (see below)
- Open a pull request against
main
Please make sure that all your pull requests are on topic, and one feature or fix per pull request makes reviewing them much faster.
Make sure you use clear, descriptive commit messages in the imperative mood.
Added full support for custom domain DNS checksFixed all subject line encryption edge cases inside the reply modal, composed modal, and forward modalUpdated readme.md to fix all spelling mistakes and grammar issues
Ensure you avoid vague messages like fixed stuff or small updates.
By contributing to any Aster repository, you agree that your contributions will be licensed under AGPL v3. Most Aster repositories are completely open source under AGPL v3.
If you have any questions, feel free to join our Discord if you would like to discuss something before opening an issue or pull request.