-
-
Notifications
You must be signed in to change notification settings - Fork 156
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
32 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
# Contributing to mcl | ||
|
||
Thank you for considering contributing to the mcl project. This document provides guidelines on how to contribute. | ||
|
||
## Bug Reports and Feedback | ||
|
||
If you find a bug, have a feature request, or have questions, please open an issue. Include the following information: | ||
|
||
- Detailed description of the problem | ||
- Steps to reproduce | ||
- Expected behavior | ||
- Actual behavior | ||
- Environment details (OS, compiler version, etc.) | ||
|
||
## Creating Pull Requests | ||
|
||
If you want to add features or make fixes, follow these steps to create a pull request: | ||
|
||
1. Fork the repository | ||
2. Create a new branch: `git checkout -b my-feature-branch` | ||
3. Make your changes | ||
4. Run tests and ensure all tests pass | ||
5. Commit your changes: `git commit -am 'Add new feature'` | ||
6. Push the branch: `git push origin my-feature-branch` | ||
7. Create a pull request | ||
|
||
When creating a pull request, clearly describe the changes and include any related issue numbers. | ||
|
||
## License | ||
|
||
mcl is released under the BSD-3-Clause License. Any code contributions will be licensed under the same license. | ||
|