Firstly, thank you for your interest in contribution. I welcome all positive changes, including bug fixes and new features. Please read this guide to ensure your contribution is a positive one.
Please send a GitHub Pull Request with a clear list of what you've changed. You can read more about pull requests here.).
Abide by the Code of Conduct when interacting with this project / repository.
Please make your commits atomic.
I use Visual Studio 2019 Enterprise, but feel free to use any IDE and environment of your choice (eg. Jetbrains Rider, ic#code SharpDevelop etc.). I will be testing your changes in Visual Studio 2019 so it may be a good idea to ensure it works as intended.
Before contributing, please check the sections below for the type of contribution you intend to create.
Please check for a pull request that may solve the issue you are trying to fix before beginning work - this will save you a lot of time!
- Open a new GitHub pull request with the patch.
- Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
- Assign me (BradF-99) for review.
- You can either send me an email, or:
- You can create a issue, and add the "features" tag, or:
- Fork the repository, and make your changes. Test them thoroughly.
- Open a new GitHub pull request with the patch.
- Ensure the PR description clearly describes the new feature.
- Assign me (BradF-99) for review.
Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of the project will generally not be accepted. However, if you make these fixes along with another contributions then that's totally fine.
- Send me an email and I'll be happy to assist.
Once again, thank you for your interest!
Brad