Prevent accidentally closing an issue if I don't have permission to reopen

[barbeque-squared]

Select Topic Area

Product Feedback

Feature Area

Issues

Body

It has happened at least once to me but I'm sure it's not the only time this has happened: you accidentally close an issue you opened in another repository (instead of hitting Comment) but you don't have permission to reopen.

I'm okay with not being able to reopen, but the UI knows that I won't have permission to reopen in that case! Having to then hope a maintainer reopens it to keep track of stuff places unnecessary strain on maintainers too.

What I propose:

• if you have permission to reopen (eg you are a maintainer on a project), clicking Close should close the issue immediately
• if you don't have permission to reopen (eg you reported a bug in another repository) have some kind of extra step that you really want to close the issue. Maybe like merge does (at least if you don't use fast forward merges) where you always need a second click.

For the vast majority of the projects I've seen, it's a maintainer (or a bot with similar rights) that closes issues, not the original reporter. I can't think any usecases where this extra verification would get in the way, but if anyone has hard statistics on issues closed by people/bots that can vs can't reopen, that would further reinforce (or debunk) my suggestion.

This is purely a UI thing, this does not impact the API.

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Zoddo]

It looks like something changed recently. Before, you were able to reopen your own issues you closed yourself. But recently, when I close an issue myself, the reopen button is grayed out.