First off, thank you for considering contributing to TLSPROXY! It's people like you that make TLSPROXY such a great tool.
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 TLSPROXY itself.
If you find a bug, please open an issue on our GitHub Issues page. Please include as much detail as possible, including your configuration, what you expected to happen, and what actually happened.
If you have an idea for a new feature or an enhancement to an existing one, please open an issue on our GitHub Issues page. This allows for a discussion of the proposed feature.
We welcome pull requests. If you'd like to contribute code, please:
- Fork the repository.
- Create a new branch for your feature or bug fix.
- Make your changes.
- Run
go generate ./...to update any generated files. - Add or update tests for your changes. Make sure all tests pass.
- Ensure your code follows the project's existing style.
- Submit a pull request with a clear description of your changes.
By contributing to TLSPROXY, you agree that your contributions will be licensed under the MIT License. A copy of the license can be found in the LICENSE file.