commit 244c98552f79a6e0810b5e50b3df391c3eec3807
from: p2r3 <41925384+p2r3@users.noreply.github.com>
via: GitHub <noreply@github.com>
date: Tue Sep 16 08:37:45 2025 UTC

add note about dev tools in contribution guidelines

commit - e88bf47d5b9a25e2faafefed2cc142d951975d89
commit + 244c98552f79a6e0810b5e50b3df391c3eec3807
blob - 4d3c7f19d381250c3ddba62ce7abd10541bc9217
blob + 16b5b0e1914e0d94ddf03bac37b19cd9d4ec9f94
--- README.md
+++ README.md
@@ -49,3 +49,4 @@ Alternatively, if you can't set up a file system, you 
 - Create issues and discuss with the maintainer(s) before making pull requests.
 - Follow the existing code style. Ensure that your changes fit in with the surrounding code, even if you disagree with the style. Pull requests with inconsistent style will be nitpicked.
 - Test your code before creating a pull request or requesting a review, regardless of how "simple" your change is. It's a basic form of respect towards the maintainer and reviewer.
+- Development tooling and compilation improvements _are not welcome,_ unless you've worked with the codebase long enough to have noticed practical shortcomings in that area. I'm tired of receiving tooling PRs from people who don't intend to work with those tools.
\ No newline at end of file