|
| 1 | +# Contributing to Curse Cloak |
| 2 | + |
| 3 | +First off, thanks for taking the time to contribute! 🎉 |
| 4 | + |
| 5 | +The following is a set of guidelines for contributing to Curse Cloak. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request. |
| 6 | + |
| 7 | +## How Can I Contribute? |
| 8 | + |
| 9 | +### Reporting Bugs |
| 10 | + |
| 11 | +This section guides you through submitting a bug report for Curse Cloak. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports. |
| 12 | + |
| 13 | +- **Ensure the bug was not already reported** by searching on GitHub under Issues. |
| 14 | +- If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring. |
| 15 | + |
| 16 | +### Suggesting Enhancements |
| 17 | + |
| 18 | +This section guides you through submitting an enhancement suggestion for Curse Cloak, including completely new features and minor improvements to existing functionality. |
| 19 | + |
| 20 | +- **Ensure the enhancement was not already suggested** by searching on GitHub under Issues. |
| 21 | +- If you find an enhancement that matches your suggestion, feel free to add your comments to the existing issue. |
| 22 | +- If you don't find an existing issue, you can open a new one. Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior. |
| 23 | + |
| 24 | +### Pull Requests |
| 25 | + |
| 26 | +The process described here has several goals: |
| 27 | + |
| 28 | +- Maintain Curse Cloak's quality |
| 29 | +- Fix problems that are important to users |
| 30 | +- Engage the community in working toward the best possible Curse Cloak |
| 31 | + |
| 32 | +Please follow these steps to have your contribution considered by the maintainers: |
| 33 | + |
| 34 | +1. **Fork** the repository. |
| 35 | +2. **Clone** your fork: `git clone https://github.com/vignesh1507/Curse_Cloak.git` |
| 36 | +3. **Create a branch** for your changes: `git checkout -b my-new-feature` |
| 37 | +4. **Make your changes**. |
| 38 | +5. **Commit your changes**: `git commit -am 'Add some feature'` |
| 39 | +6. **Push to the branch**: `git push origin my-new-feature` |
| 40 | +7. **Create a new Pull Request**. |
| 41 | + |
| 42 | +### Code of Conduct |
| 43 | + |
| 44 | +This project and everyone participating in it is governed by the Curse Cloak Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected]. |
| 45 | + |
| 46 | +Thank you for contributing to Curse Cloak! |
0 commit comments