# Contributing to Splunk MCP
First off, thank you for considering contributing! Your help is appreciated.
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.
## How Can I Contribute?
There are many ways to contribute, from writing tutorials or blog posts, improving the documentation, submitting bug reports and feature requests or writing code which can be incorporated into Splunk MCP itself.
* **Reporting Bugs:** If you find a bug, please report it.
* **Suggesting Enhancements:** Have an idea for a new feature or improvement? Let us know!
* **Pull Requests:** If you want to contribute code, documentation, or other changes directly.
## Reporting Bugs
Before creating bug reports, please check existing issues as you might find out that you don't need to create one. When you are creating a bug report, please include as many details as possible. Fill out the required template, the information it asks for helps us resolve issues faster.
Include:
* A clear and descriptive title.
* A detailed description of the problem, including steps to reproduce the bug.
* Your environment details (Splunk version, Python version, OS, etc.).
* Any relevant logs or error messages.
## Suggesting Enhancements
If you have an idea for an enhancement:
* Explain the enhancement and why it would be useful.
* Provide as much detail as possible about the suggested implementation or desired behavior.
* Feel free to provide code snippets or mockups if applicable.
## Pull Request Process
1. **Fork the repository:** Create your own copy of the repository.
2. **Create a branch:** Create a new branch for your changes (`git checkout -b feature/AmazingFeature`).
3. **Make your changes:** Implement your feature or bug fix.
* Adhere to the existing code style.
* Add tests for your changes if applicable.
* Ensure all tests pass.
4. **Commit your changes:** Use clear and concise commit messages (`git commit -m 'Add some AmazingFeature'`).
5. **Push to your branch:** (`git push origin feature/AmazingFeature`).
6. **Open a Pull Request:** Submit a pull request to the main repository's `main` branch.
* Provide a clear description of the changes.
* Link any relevant issues.
## Code of Conduct
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. (We should create a `CODE_OF_CONDUCT.md` file if needed).
## License
By contributing, you agree that your contributions will be licensed under the Apache License 2.0, as found in the `LICENSE` file.