Can't close an issue of author "ghost"

[AiyionPrime]

Select Topic Area

Bug

Feature Area

Issues

Body

In the repo freifunk-gluon we've got some outdated issues I'd like to mark as resolved.
This was not a problem before, but now is, when I'd like to add an explanation.

freifunk-gluon/gluon#923

I'd like to close this with the following comment:

While this had relevance in the past,
I think this has been taken care of in [features/wired-mesh](https://gluon.readthedocs.io/en/latest/features/wired-mesh.html).

As the author is now gone, I'd close this and invite other interested users to follow up on this in case they find the now existing documentation still lacking.

To the now anonymous author:
Thanks for your interest in making gluon better!

But regardless of whether I use firefox or chromium, I hit the same network error and no comment appears.

Uncaught TypeError: o is null
    optimisticResponse add-comment-mutation.ts:58
    Q add-comment-mutation.ts:188
    Q IssueCommentComposer.tsx:171
    J IssueCommentComposer.tsx:297
    onClick IssueActions.tsx:439
    React 11
add-comment-mutation.ts:58:33
    optimisticResponse add-comment-mutation.ts:58
    Q add-comment-mutation.ts:188
    Q IssueCommentComposer.tsx:171
    J IssueCommentComposer.tsx:297
    onClick IssueActions.tsx:439
    React 11

I can close the issue, but can't comment, though I'm one of the organizations owners.

If there is more info I should share, please let me know.
Thanks for your time!

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. ⭐

[mmdiego]

I'm having the same problem in another repository where I can't comment on any issues that now belong to the ghost user.

[AiyionPrime]

In case it's public and you don't mind, you could link it here, so that admin might assess it.

[mmdiego]

Sure, here's one of the failing issues: openquantumhardware/qick#338

Some more information: I was able to add a comment using Gitlab-CLI: gh issue comment... and then edited it from the Web

[mmdiego]

I'm able to comment again in ghost issues. @AiyionPrime can you check if it's also working for you as well?

[AiyionPrime]

Yes indeed. Thanks for letting me know!