Bug reporting process seems rigid

[SanjoSolutions]

The bug reporting process seems to be a bit rigid. I have tried to report a bug #80772. The process requires a reproduction repo, which in the case seemed unnecessary. As a result me not willing to create a "reproduction repo" without any meaning to me, I receive a "automatically closed" message (which was transparently communicated that it will happen).
This rigid process makes it unattractive to me to contribute any further to this project.

I recommend to allow more open feedback without requirements to spend tens of minutes potentially to do work, just to report a bug. This seems more respectful to potential contributors and seems to make more sense than to push potential contributors away by "requiring" work to be done, before a bug can be reported.

[icyJoseph]

Hi,

This is why the discussions board exists. IIRC an issue can be made of a discussion, and from a discussion a PR can be made anyway, or the issue be raise to core devs. The issues channel is not the only channel.

[icyJoseph]

The problem's potentially here, https://github.com/vercel/next.js/blob/canary/packages/next/src/lib/eslint/writeDefaultConfig.ts#L10 - still investigating