:balloon: Thanks for your help improving the project!
Do you have an improvement?
When initially submitting a pull request, we prefer a single squashed commit. It is preferable to split up contributions into multiple pull requests if the changes are unrelated. All pull requests are squashed when merged, but squashing yourself gives you better control over the commit message.
After the pull request is submitted, all changes should be done in separate commits. This makes reviewing the evolution of the pull request easier. We will squash all the changes into a single commit when we merge the pull request.
Finalized commit messages should be in the following format:
Subject Problem Solution Validation
bad: server disconnects should cause dst client disconnects. good: Propagate disconnects from source to destination
bad: support tls servers good: Introduce support for server-side TLS (#347)
Explain the context and why you‘re making that change. What is the problem you’re trying to solve? In some cases there is not a problem and this can be thought of as being the motivation for your change.
Describe the modifications you've made.
Describe the testing you've done to validate your change. Performance-related changes should include before- and after- benchmark results.