Github could tweak the tools available to make this easier for maintainers to manage I think, for example: — a setting to allow PRs but only if they already pa

Github could tweak the tools available to make this easier for maintainers to manage I think, for example: — a setting to allow PRs but only if they already pass all tests & linting (using a Dockerfile supplied by the source repo). You're PR doesn't show up on the radar for the maintainer until it's already some way mergeable (and you can't edit the build agent). — allowing issues only in the form of a PR with a new failing test case (again, ran through the pipeline created by the maintainer). Also, allowing a repo maintainer to have required fields in an issue form rather than having a template that may or may not get followed. — some type of settings that maintainers can turn on to enable "Kudos" or thank you posts, separate to the issue tracker. Maintainers could ask for/enforce all of those things at the moment manually, but it's putting all the friction onto their plate (rather than the people offering fly-by criticism).