Help us understand the severity of this issue

• breakage; unable to contribute or trigger builds will no workarounds
• inconvenient workarounds exist, but significant effort required
• needed for a Flutter team-wide priority (already agreed upon)
• nice-to-have; none of the above

What do you need help with

Currently, we are using a personal fork of the no-response bot to auto-close issues where the reporter doesn't get back to us with information we need to make it actionable. The fork exists because we needed a fix to it at some point, and the upstream version appeared to be abandoned—which still seems to be the case.

Since it's an important part of our issue workflow, and there's no sign that we will be able to revert to an upstream version, we should make a team-owned fork and point to that, instead of relying on a personal repo.