Hello! We're thrilled that you're interested in contributing to DevOption. Your help is essential for keeping it great.
Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.
This section guides you through submitting a bug report for DevOption. Following these guidelines helps maintainers understand your report, reproduce the behavior and find related reports.
- Check the Issues to see if the bug has already been reported. If it has, add a comment to the existing issue instead of opening a new one.
- When you are creating a bug report, please include as many details as possible.
- Write clear, concise steps to reproduce the issue. Include screenshots if necessary.
This section guides you through submitting an enhancement suggestion for DevOption, including completely new features and minor improvements to existing functionality.
- When you are creating an enhancement suggestion, please include as many details as possible and consider including code examples.
- Don't forget to check if your idea is compatible with our project's roadmap and whether it fits into the scope of the features we're planning.
Pull Requests are always welcome.
- Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
- Before submitting the PR, please make sure your code follows the Laravel coding standards and your changes are covered by tests.
- Please include issue numbers in the PR title.
- Keep your PRs as simple as possible, i.e., if you're adding two different features, make two different PRs.
- Write good commit messages.
// Here you can include instructions on how to setup the development environment.
If you have any questions, please feel free to contact us.
Thanks! Happy coding!