Before opening a PR, open or find an issue and discuss the proposed change with a maintainer. When there is reasonable consensus between humans on how to implement the feature or solve the bug, then a PR is welcome.
You will know that reasonable consensus was reached when the label ready-for-pr is added to the issue.
Refer to our contributor guide located in the iroh repo for more details.
Keep summaries and descriptions in issues, PRs, and comments concise and on topic. Any content should have the length and depth of a natural, human-to-human conversation. Additional AI-assisted content should be enclosed in a <details>...</details> section and the issue should be meaningful without it. Excessive AI-looking prose will not be allowed.
If you are using LLMs to translate from your native language into English, please let us know, and we welcome you to post both your original writing (in your native language) and the LLM translation.
You are responsible for everything you submit, regardless of how it was produced. You must be able to explain your motivation for every change in your PR during review. PRs where the author cannot do so may be closed.