Skip to content

Latest commit

 

History

History
37 lines (23 loc) · 1.86 KB

CONTRIBUTING.md

File metadata and controls

37 lines (23 loc) · 1.86 KB
Raw

Contributing to BlazoryVS

Thank you for your interest in contributing to BlazoryVS! We welcome contributions from the community to help make this project better.

Reporting Issues

If you encounter any issues while using BlazoryVS, please check the issue tracker to see if your issue has already been reported. If not, you can open a new issue with the following information:

  • A clear and concise title.
  • A detailed description of the issue, including steps to reproduce it.
  • Any relevant error messages or screenshots.

Pull Requests

We encourage you to contribute to BlazoryVS by submitting pull requests for bug fixes, improvements, or new features. Here's how to do it:

  1. Fork the BlazoryVS repository on GitHub.
  2. Create a new branch for your changes: git checkout -b feature-or-fix-name.
  3. Make your changes and commit them with clear and concise messages.
  4. Push your changes to your fork: git push origin feature-or-fix-name.
  5. Create a pull request from your fork to the main branch of BlazoryVS.

Please follow these guidelines when creating pull requests:

  • Ensure your code is well-documented and follows the project's coding style.
  • Provide a clear description of your changes in the pull request.
  • If your pull request addresses an issue, reference that issue in the description.

Development Setup

To set up a development environment for BlazoryVS, follow the instructions in the README.

Code of Conduct

Please review our Code of Conduct before participating in the BlazoryVS community.

We appreciate your contributions and look forward to working together to improve BlazoryVS!