The placeholder username of admin-posted discussions is very confusing

[typed-sigterm]

Discussion Type

Bug

Discussion Content

When a discussion is posted as admin, it's shown as <OWNER_NAME> Admin and the avatar is the repo owner's avatar.

It seems to be okay here:

But how about this:

There's two problems:

1. The repo is owned by a peronsal account, what's the meaning of John Doe Admin?
2. As the blog describes, the feature only requires admin permission of the repo, not the org. That's saying collaborators can do that, not the admin of the org

This feature actually introduced an "anonymous" identity system in the discussion, but it doesn't seem to have been properly designed and appears to have been rushed out :(

[Archit086]

This is a fair concern. If the repository is owned by a personal account, calling someone “John Doe Admin” is confusing because there is no organization context there, so the label doesn’t really mean anything. On top of that, the blog itself says the feature only checks for admin permission on the repository, not admin rights on the organization, which means any collaborator with admin access could appear under this anonymous “Admin” identity. That makes the naming misleading and blurs the line between actual org admins and regular repo collaborators. It really does feel like an anonymous identity layer was added to discussions without clearly defining the roles or edge cases, and the whole thing looks a bit rushed and under-thought.

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