Closing and LOCKING stale PRs via bot, which is bad UX
What version of Codex is running?
n/a
Which model were you using?
n/a
What platform is your computer?
n/a
What steps can reproduce the bug?
https://github.com/openai/codex/pull/564#issuecomment-3162194202
https://github.com/openai/codex/pull/206#issuecomment-3162178580
What is the expected behavior?
Often, people follow issues or PRs on GitHub because they are interested in the bufix/feature and want to get updates when it is resolved. Having a bot not only close, but fully lock conversation is fairly uncouth open source behavior. I now need to what, scan the issue/PR list?
Even if you closed these PRs as stale, I would still be following them and if someone opened a new PR or issue with the request, there's a high chance I would see it on the old PR, get the notification, and know which additional items to follow. This leads to a poor user experience.
What do you see instead?
Do not lock PRs that are closed as out of date/stale.
Additional information
_No response_